feat(lm-logs): default cri tail parser, optional monitor agent, and input validation#223
Merged
Conversation
lm-aditya-kadam
requested review from
choudharypooja,
lmshubhashri and
lmvaibhavk
as code owners
lm-aditya-kadam
changed the title
Use kubernetes.containerTailParserType (default cri) so kubernetes.conf emits a valid <parse>@type cri block for containerd/CRI-O logs. Keep multi_format + patterns as optional via Helm value. Bump chart to 1.1.0-rc02.
* feat(lm-logs): add configurable monitor_agent for buffer metrics Add fluent.monitorAgent config block to expose Fluentd plugin/buffer metrics via HTTP when enabled. Conditionally inject <source @type monitor_agent> into ConfigMap and expose containerPort on DaemonSet when enabled. Changes: - Add fluent.monitorAgent config (enabled, bind, port) in values.yaml - Conditionally include <source> block in configmap.yaml template - Conditionally expose containerPort in deamonset.yaml template - Update values.schema.json with monitorAgent field definition - Bump chart version to 1.1.0-rc04 Feature disabled by default. Enable by setting: lm-logs: fluent: monitorAgent: enabled: true bind: 0.0.0.0 port: 24220 * feat(lm-logs): add configurable monitor_agent for buffer metrics Add fluent.monitorAgent config block to expose Fluentd plugin/buffer metrics via HTTP when enabled. Conditionally inject <source @type monitor_agent> into ConfigMap and expose containerPort on DaemonSet when enabled. Changes: - Add fluent.monitorAgent config (enabled, bind, port) in values.yaml - Conditionally include <source> block in configmap.yaml template - Conditionally expose containerPort in deamonset.yaml template - Update values.schema.json with monitorAgent field definition - Bump chart version to 1.1.1-rc01
ct / yamllint require a newline at end of chart.yaml. Without it, chart-testing fails on rule new-line-at-end-of-file. Co-authored-by: Cursor <cursoragent@cursor.com>
lm-aditya-kadam
force-pushed
the
lm-logs/1.1.1
branch
from
d41b198 to
43d63f3
Compare
lmshubhashri
approved these changes
May 19, 2026
Contributor
|
merging on behalf of @lm-aditya-kadam |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CRI container log parser — kubernetes.containerTailParserType defaults to cri and the generated tail into
block uses @type cri when selected, which aligns with containerd/CRI-O log format and avoids
relying on FLUENT_CONTAINER_TAIL_PARSER_TYPE for the common case. multi_format remains available for
legacy or mixed environments.
Monitor agent — fluent.monitorAgent (enabled/bind/port) injects a monitor_agent
fluent.conf and exposes the chosen port on the DaemonSet when enabled, so operators can scrape or
port-forward to /api/plugins.json and related endpoints.