Skip to content
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

InfluxDB(2)Writer does not fully print error from InfluxDB(2). Maybe it should #10072

Open
RincewindsHat opened this issue Jun 6, 2024 · 0 comments
Labels
area/influxdb Metrics to InfluxDB area/log Logging related

Comments

@RincewindsHat
Copy link
Member

Is your feature request related to a problem? Please describe.

While debugging problems with a spurious bug in the InfluxDB connection of Icinga2 I had some trouble to find the original problem and it would have been helpful if, instead of
just printing

[2024-06-06 18:05:26 +0200] warning/Influxdb2Writer: Unexpected response code: Bad Request
Context:
	(0) Processing check result for 'some-host!some-service'

[2024-06-06 18:05:26 +0200] warning/Influxdb2Writer: Unexpected Content-Type: application/json; charset=utf-8
Context:
	(0) Processing check result for 'some-host!some-service'

it would actually print the HTTP body with something like this:

{"code":"invalid","message":"unable to parse blablabalbla,metric=bla value=-inf 1717686350': invalid number"}

Describe the solution you'd like

Printing the full HTTP body would be nice.

@Al2Klimov Al2Klimov added area/log Logging related area/influxdb Metrics to InfluxDB labels Jun 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/influxdb Metrics to InfluxDB area/log Logging related
Projects
None yet
Development

No branches or pull requests

2 participants