-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Weird opentelemetry-collector errors #26343
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Also filed here: #opentelemetry-collector/issues/8340 |
hm... I am sure I have seen this in the past. But looking at the stacktrace and impl. I can only guess what might have caused it. A closer look with a real debugger might help. Could you provide some details about the passed objects? |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Same problem here with wildfly 30. |
getting the same error too. Have tried collectors from 0.82.0 to 0.90.0. All the same. |
@andrm, @fede843, or @ghevge: Would you be able to provide the detailed information about the passed objects that the logger is hitting the errors on, as @frzifus requested above? This would be very helpful in debugging, otherwise it will be hard to make progress. |
@crobert-1 it will probably be faster to change otel-collector and throw those packages in the logs, in debug mode. |
Pardon my ignorance, but I don't understand what you mean here. Since this isn't failing every time the goal is to find what data is causing this exception to be hit, helping us understand the root cause and fix it. Are you suggesting adding more logging to the collector to understand which packages are causing the failure? Either way, any more information that can be provided here would be helpful. |
Yes. This will also make any future investigations much faster IMO |
I'm getting this from wildfly 30:
It's very confusing, how does the collector know the comment? From prometheus? |
It looks like a concurrency issue. I issue the same curl command twice and I different entries for the same counter:
Is this a wildfly problem? |
Is there a way to debug what wildfly is sending? |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I'm having the same issue with Wildfly 30 publishing to the collector
otel-collector-config
|
I bumped into this problem now too while using the jenkins open-telemetry plugin. Config:
yields (note censored version):
|
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
It seems that this is the error that the Wildfly users are experiencing: https://issues.redhat.com/browse/WFLY-18300. It would probably not hurt to give it a vote. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
exporter/prometheus
What happened?
I'm trying to set up opentelemetry-collector with prometheus, tempo and loki on a dockerize jave springboot 3 application.
I've managed to start all the containers, but once I generet some activity on my app, otel collector start to generate errors like bellow:
Any idea what could be causing this?
Collector version
0.82.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
OpenTelemetry Collector configuration
Log output
Additional context
My docker-compose looks something like this:
Java config class:
application.yaml:
The text was updated successfully, but these errors were encountered: