weiqingy opened a new issue, #541: URL: https://github.com/apache/flink-agents/issues/541
### Search before asking - [x] I searched in the [issues](https://github.com/apache/flink-agents/issues) and found nothing similar. ### Description ## Summary Add per-event-type configurable log levels to the event log system, as identified in the 0.3 planning discussion (#516). ## Motivation The current event log system only supports binary accept/reject filtering via `EventFilter`. There is no way to: - Configure different log levels for different event types (e.g., VERBOSE for ChatRequestEvent, OFF for ContextRetrievalRequestEvent) - Distinguish between standard and verbose logging detail (both behave identically) - Filter logged events by level or event type in downstream tools without parsing nested JSON ## Changes - New `EventLogLevel` enum: `OFF`, `STANDARD`, `VERBOSE` - Per-event-type levels configured via `EventLoggerConfig` builder and string-based config options - STANDARD truncates long string fields (configurable `eventLogMaxFieldLength`, default 1024); VERBOSE logs full content - Top-level `eventType` field in JSON output for easier downstream filtering - Startup validation warns about unrecognized event type names in config - Backward compatible: existing configs and JSON format continue to work ## Config Options | Key | Default | Description | |-----|---------|-------------| | `eventLogLevel` | `STANDARD` | Global default level (OFF, STANDARD, VERBOSE) | | `eventLogLevels` | (none) | Per-type overrides. Format: `ChatRequestEvent=VERBOSE,InputEvent=OFF` | | `eventLogMaxFieldLength` | `1024` | Max chars for string fields at STANDARD level. 0 disables truncation. | ## Related - Discussion #516 (Planning Flink Agents 0.3) ### Are you willing to submit a PR? - [ ] I'm willing to submit a PR! -- 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]
