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
The Helm chart for OpenSearch Dashboards uses the app label, which causes object mapping issues in Fluent Bit. Fluent Bit expects the app field to be an object, but a simple value is provided instead. This conflict results in errors during log processing and indexing in OpenSearch Dashboards.
To Reproduce
Steps to reproduce the behavior:
Deploy the Helm chart for OpenSearch Dashboards.
Configure Fluent Bit to forward logs to OpenSearch.
Observe the logs in Fluent Bit.
Expected behavior
Fluent Bit should correctly process and forward logs without any object mapping conflicts.
The app label should not cause any issues with log processing.
Chart Name
opensearch-dashboards
Screenshots
If applicable, add screenshots to help explain your problem.
{
"type": "mapper_parsing_exception",
"reason": "object mapping for [kubernetes.labels.app] tried to parse field [app] as object, but found a concrete value"
}
Host/Environment (please complete the following information):
Helm Version: 2.24.1
Kubernetes Version: v1.29.3
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
The Helm chart for OpenSearch Dashboards uses the app label, which causes object mapping issues in Fluent Bit. Fluent Bit expects the app field to be an object, but a simple value is provided instead. This conflict results in errors during log processing and indexing in OpenSearch Dashboards.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Chart Name
opensearch-dashboards
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: