Skip to content
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions deploy-apps/streaming-logs.html.md.erb
Original file line number Diff line number Diff line change
Expand Up @@ -97,6 +97,10 @@ For more information about Zipkin tracing, see [Zipkin tracking in HTTP headers]

Loggregator emits `LGR` logs to indicate problems with logging. Examples include `can't reach syslog drain url` and `dropped log messages due to high rate`.

### <a id='sys'></a> SYS

The Syslog Agent emits `SYS` logs to indicate problems with syslog drain delivery. This log type is emitted alongside `LGR` logs when messages are dropped due to slow drain consumption or connectivity issues. The `SYS` source type includes the source index of the Syslog Agent instance.

### <a id='app'></a> APP

Every app emits `APP` logs to Loggregator.
Expand Down Expand Up @@ -149,6 +153,10 @@ For example:
2016-06-14T13:44:38.14-0700 [CELL/0] OUT Successfully created container
</pre>

### <a id='health'></a> HEALTH

The Diego Cell emits `HEALTH` logs when running health check actions for an app. These logs are generated by the health check binary that monitors app instances. By default, health check log output is suppressed unless an error occurs.


## <a id='writing'></a> Writing to the log from your app

Expand Down