Skip to content

Commit 8469f39

Browse files
chombiumjorbaum
andcommitted
Clean up docs about SYS log type
In the meantime, the `SYS` log type was removed in the Syslog Agent's code. Co-authored-by: Joris Baum <joris.baum@sap.com>
1 parent 5b069d2 commit 8469f39

1 file changed

Lines changed: 0 additions & 4 deletions

File tree

deploy-apps/streaming-logs.html.md.erb

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -97,10 +97,6 @@ For more information about Zipkin tracing, see [Zipkin tracking in HTTP headers]
9797

9898
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`.
9999

100-
### <a id='sys'></a> SYS
101-
102-
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.
103-
104100
### <a id='app'></a> APP
105101

106102
Every app emits `APP` logs to Loggregator.

0 commit comments

Comments
 (0)