-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
Post to /influxapi produce an error #462
Comments
Hello @Friz-zy
worked. Can you share some information about what inputs you're using? |
@lmangani this problem appears just when |
@Friz-zy Couldn't reproduce your case locally with a small local setup. I'll send a couple of issues into your github repo as I can't make it start. |
@akvlad I created a branch for you
|
@Friz-zy thanks. Will check and fix the issue. |
Hello @Friz-zy I have one suggestion for the error you experience.
Is it possible that you send a gzipped body without the appropriate header?
That is the only case when I see a similar error as you provide.
|
@Friz-zy fixed: Friz-zy/qryn-docker-s3#1 |
@akvlad that works, thank you. But but I'm seeing some strange behavior in the metric names: when I use @lmangani possibly need to update docs with examples how to connect collectors using login & password. Also I can update my fork and open a pull request to your original repo qryn-docker-s3 |
@Friz-zy As far as I understand |
@akvlad yeah, |
@Friz-zy It's about the format of influx -> prometheus conversion. We may reconsider the feature. |
@akvlad yeah, I can totally picture it. After victoriametrics it is unusual for me, but ideologically this variant may be more correct. Although again telegraf itself generates metrics for Prometheus exactly in the |
Can this issue be closed? |
I'm testing latest
qxip/qryn:bun
with telegraf. I have a problem with password authorization:When telegraf is configured with "Authorization" header in
outputs.influxdb_v2
qryn produce
metric parse error
Possibly this is a problem real metrics parsing because simple curl request works fine
When I tried url substitution in telegraf config
then telegraf just can't pass the authorization
Curl request works fine
Qryn is configured to use
test
as admin login and passwordThe text was updated successfully, but these errors were encountered: