TLDR Ioannis encountered a 404 error and asked for assistance. Prabhat confirmed a bug, which was later fixed by Patel. Assen also found discrepancies in the documentation, which Prabhat corrected.
for reference the setup is
```exporters:
prometheusremotewrite:
endpoint:
replacing sensitive values ofc :slightly_smiling_face:
in all actual honesty..
Thanks you for report this, we will quick fix it
Hengfei no worries. I guess I can try the container in the meantime? Also, who can answer some questions about pricing?
Prabhat Let you answer the questions about pricing
> in all actual honesty..
sure
I am also trying to make this work.
Assen You may have an @ or : symbol possibly in the token. Try regenerating the token.
my user name is my email address, so yes, there's an @
yeah, apart from that
Are you using one of the code examples for opentelemetry from
Actually you should not have any no-numeric characters in ingestion token
we made sure of that when generating the token
unless it's not working well 100% of the time
Thanks! I am configuring an OTLP collector - no code - but your link helped. it brought me to
I am trying to send metrics, no traces BTW
```exporters:
prometheusremotewrite:
endpoint: "
is this working?
no, ``` "error": "Permanent error: Permanent error: remote write returned HTTP status 401 Unauthorized; err = %!w(<nil>): {\"Error\":\"Authentication failed - invalid token: token contains an invalid number of segments\"}"```
Let me check in my config
I can confirm that we have a problem. The URL and config are correct, but its not working due to a bug. The problem is only in cloud deployment. Open source version works well. Will fix it soon.
Will confirm it here once fixed.
Thanks for checking!
Assen Can you please check now? it should work now
that was amazingly fast! Thanks a lot Patel!
It works for me, but it would be useful to change
Thanks for pointing the issue. Fixed it.
Ioannis
Thu, 08 Jun 2023 19:24:28 UTCHey folks. I followed the guide on how to setup OTel for metrics, but I am getting a 404 each time the exporter hits the endpoint - any idea why?