joeyutong commented on code in PR #924: URL: https://github.com/apache/flink-agents/pull/924#discussion_r3702335984
########## docs/content/docs/operations/monitoring.md: ########## @@ -240,7 +251,7 @@ Example record at `STANDARD` with a long string and a large array truncated: ### Per-event-type log levels -You can override the level for individual event types using the `event-log.type.<EVENT_TYPE>.level` config key, where `<EVENT_TYPE>` is the event's routing type string (the same string that appears as `eventType` in the JSON log). Built-in events use short snake-cased names such as: +You can override the level for individual event types using the `event-log.type.<EVENT_TYPE>.level` config key, where `<EVENT_TYPE>` is the event's routing type string (the same string that appears as `eventType` in the JSON log). Although the field name uses camelCase, built-in Event type values remain snake-cased: Review Comment: Agreed. I added all four execution lifecycle routing types to the per-event-type table and documented the composition explicitly: `event-log.trace.enabled` controls whether lifecycle Events are produced, while the normal per-type level resolution still applies once Trace is enabled. Setting an `_execution_*` type to `OFF` therefore suppresses that lifecycle Event and may make the recorded Trace incomplete. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
