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
Describe the bug
This bug is similar to issue in OpenTelemetry Collector: open-telemetry/opentelemetry-collector-contrib#28806
Logs which are forwarder to Loki from Event Hub through Promtail does not have any category for ApplicationGatewayFirewallLog even though it is visible in Event Hub message.
Check if category is missing even though logs are visible in Loki/Grafana
Expected behavior
Proper category should be assigned/relabeled by Promtail in Loki for ApplicationGatewayFirewallLog even when only timeStamp filed is available in message.
Environment:
Infrastructure: Azure Container Apps
Deployment tool: Docker
Screenshots, Promtail config, or terminal output
Promtail config below:
Describe the bug
This bug is similar to issue in OpenTelemetry Collector: open-telemetry/opentelemetry-collector-contrib#28806
Logs which are forwarder to Loki from Event Hub through Promtail does not have any category for ApplicationGatewayFirewallLog even though it is visible in Event Hub message.
It is probably happening due to missing time field and relabel not properly working:
https://github.com/grafana/agent/pull/3412/files#diff-f7b899798d7f7b22d9a64584a767fa07952fa917226e312ad088de922ea06e71R37
Only timeStamp field is available for ApplicationGatewayFirewallLog.
Normal message from Application Gateway with proper category relabel looks like this:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Proper category should be assigned/relabeled by Promtail in Loki for ApplicationGatewayFirewallLog even when only timeStamp filed is available in message.
Environment:
Screenshots, Promtail config, or terminal output
Promtail config below:
The text was updated successfully, but these errors were encountered: