-
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
influxes receiver might need more endpoints #33817
Comments
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. |
@open-telemetry/collector-contrib-triagers I'm all for "auto closing issues" when the answer is "we won't do this, but feel free to make a PR" but if no response is given, it makes it hard to know what to do next here. |
Sorry @skandragon this is all automated management. @jacobmarble any chance you can weigh in? @skandragon would you be interested to provide a fix or help create a test reproducing the issue? |
Component(s)
receiver/influxdb
What happened?
Description
I'm trying to point my Proxmox cluster to the influxes receiver, but it fails to add. It attempts to do a
GET /health
which is most likely some sort of initial probe test. It then fails to add the metric feed.Steps to Reproduce
Expected Result
Actual Result
Collector version
v0.103.0
Environment information
Environment
Proxmox
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: