diff --git a/deploy-apps/streaming-logs.html.md.erb b/deploy-apps/streaming-logs.html.md.erb
index 4e9e956d..a3ef025b 100644
--- a/deploy-apps/streaming-logs.html.md.erb
+++ b/deploy-apps/streaming-logs.html.md.erb
@@ -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.
@@ -149,6 +153,20 @@ 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='proxy'></a> PROXY
+
+Every app container includes an Envoy sidecar proxy that handles the mTLS handshake with the Gorouter and proxies traffic to the app process. The Envoy sidecar emits `PROXY` logs. By default, Envoy runs with a critical log level, so `PROXY` logs mainly appear when Envoy encounters critical errors, fails to start, or is killed due to the container running out of memory.
+
+For example:
+
+<pre class="terminal">
+2026-01-26T13:49:18.72+0000 [PROXY/0]     OUT Exit status 137 (out of memory)
+</pre>
+
 
 ## <a id='writing'></a> Writing to the log from your app