You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of #556 the support for tailing application logs from the container runtime is needed. This is essential to achieve feature parity with the current solution based on fluentbit.
Criterias
If the application input gets enabled together with an OTLP output, the new log agent gets deployed
The application input is enabled by default
The agent will collect all application logs as it was the case with fluenbit (using selectors)
The agent will pars json formats if possible
The agent will enrich severity and timestamp OTLP attributes
The body contain either the JSON msg/message attribute or the raw payload
Support of "keepRawPayload" feature by having an additional log attribute with the raw payload
The agent might stay deployed if the input gets disabled
Kubernetes attribute enrichment should work in conjunction with the gateway
Metric collection for operations should work (have a metric service and peerauthentication in place)
The text was updated successfully, but these errors were encountered:
a-thaler
changed the title
If the tail input is enabled, deploy a log agent which maps the logs to OTLP
OTLP Logs: Deploy a log agent which tails logs and maps them to OTLP
Dec 16, 2024
Description
As part of #556 the support for tailing application logs from the container runtime is needed. This is essential to achieve feature parity with the current solution based on fluentbit.
Criterias
The text was updated successfully, but these errors were encountered: