-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Collector complains about "Could not dynamically add mapping for field [http.connection.id]" #1866
Comments
This seems to be related to the envoy access logs and #1768 |
Can you do a |
I did and got the same problem. I'm running Docker on x86_64, Ubuntu. |
I'm seeing this same error and it's causing the logs not to show up in opensearch. Deleted all images, volumes, ran prune. Same error.
|
Hi @TrevorSquillario, does the fix in #1930 work for you, to disable a bunch of attributes in the Envoy access logs? |
Bug Report
Which version of the demo you are using?
Using main latest:
$ git log
commit e3548c6 (HEAD -> main, upstream/main)
Date: Sun Dec 22 08:49:02 2024 -0500
Symptom
Collector batchprocessor and opensearch exporter complains about
Could not dynamically add mapping for field [http.connection.id]
Existing mapping for [attributes.http] must be of type object but found [text]
What is the expected behavior?
No complains.
Reproduce
Could you provide the minimum required steps to resolve the issue you're seeing?
docker compose build
docker compose run
docker compose logs otel-collector
Workaround
Disable logs pipeline in the Collector.
Additional context
Related to #1833
However, this occurs with standard demo components without enabling any vendor backends.
The text was updated successfully, but these errors were encountered: