# Log Files

A service in a project may define log files. These log files may be from the
standard output, the standard error, a file inside of the service container
or the output of a utility command inside the service container.

These can be configured using the `logging` attributes of a {doc}`/config_docs/entities/services`.

## `riptide log`

Riptide has a builtin command to view log files: `riptide log`. Using the `-s` flag you can filter specific
services and using the `-l` flag you can filter specific log files. There are also more options, like following the
log output (`-f`). See `riptide log --help` for more information.

### Example

```ansi-console
$ riptide log -f
cypress stdout       | [STARTED] Task without title.
cypress stdout       | [SUCCESS] Task without title.
opensearch stderr    | WARNING: Please consider reporting this to the maintainers of org.opensearch.bootstrap.Security
opensearch stderr    | WARNING: System::setSecurityManager will be removed in a future release
cypress stderr       |     at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:344)
cypress stderr       |     at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:266)
cypress stderr       |     at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:521)
cypress stderr       | 
rabbitmq stdout      | 2025-11-26 14:43:50.160652+00:00 [info] <0.546.0>  * rabbitmq_management_agent
rabbitmq stdout      | 2025-11-26 14:43:50.160652+00:00 [info] <0.546.0>  * rabbitmq_web_dispatch
rabbitmq stdout      | 2025-11-26 14:43:50.237087+00:00 [info] <0.9.0> Time to start RabbitMQ: 6529 ms
opensearch stdout    | [2025-11-26T18:58:51,805][INFO ][o.o.j.s.JobSweeper       ] [riptide] Running full sweep
opensearch stdout    | [2025-11-26T19:03:51,805][INFO ][o.o.j.s.JobSweeper       ] [riptide] Running full sweep
varnish stderr       | Debug: Version: varnish-7.4.3 revision b659b7ae62b44c05888919c5c1cd03ba6eaec681
varnish stderr       | Debug: Platform: Linux,6.12.57,x86_64,-junix,-smalloc,-sdefault,-hcritbit
varnish stderr       | Debug: Child (42) Started
varnish stderr       | Child launched OK
varnish stderr       | Info: Child (42) said Child starts
db stdout            | 2025-11-26 14:43:43+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
db stdout            | 2025-11-26 14:43:43+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.44-1debian12 started.
db stderr            | 2025-11-26T14:43:43.970865Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.44'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server - GPL.
db stderr            | mbind: Operation not permitted
```

## View files manually

You can also view the log files directly:
open the directory `<project>/_riptide/logs/`.

You will find a directory in there for each service that defines logs.
Inside the directories are the log files.

Log files don't get cleared after a service reboots. If you want to clear them
manually, stop the service and remove the files.