You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to Prometheus' documentation on "Remote Endpionts and Storage" only "remote write" support for OpenTSDB is available. What is the current status for supporting Prometheus' remote read support?
Is this a feature that is in the works? (I did a search against the issues here, but did not find any)
Is this to be worked on for the OpenTSDB 2.x or 3.x branch?
Hopefully this is the right place for this question.
A quick internet search shows some grass root attempts or inquiries but none of them are viable options.
The most promising lead I could find was geras. But that build is currently failing and it is a relative new project. If there are other viable options I should look at, I am all ears.
Thanks!
The text was updated successfully, but these errors were encountered:
We didn't have an API that would satisfy Prometheus' requirements I'm guessing as they likely want to push down a lot of functions to the remote. This should be easy to add with 3.x as we now have a Prometheus plugin that will accept PromQL. It's still alpha though and I need help testing it.
According to Prometheus' documentation on "Remote Endpionts and Storage" only "remote write" support for OpenTSDB is available. What is the current status for supporting Prometheus' remote read support?
Is this a feature that is in the works? (I did a search against the issues here, but did not find any)
Is this to be worked on for the OpenTSDB 2.x or 3.x branch?
Hopefully this is the right place for this question.
A quick internet search shows some grass root attempts or inquiries but none of them are viable options.
The most promising lead I could find was geras. But that build is currently failing and it is a relative new project. If there are other viable options I should look at, I am all ears.
Thanks!
The text was updated successfully, but these errors were encountered: