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
First of all hello and thank you very much for sharing this very cool project!
I think it would be nice to support the ability to fetch metrics held in the Prometheus server which are not usually exposed any other way. For instance alerts and recording rules.
I have found a workaround for this use case, if anyone is interested, to scrape the /federate endpoint and passing the correct "instant vector selector" and url-encoding the query.
For instance, let's say that your metric is named candies (could be a recording rule aggregating and manipulating other primitive metrics), then you can invoke prometheus-to-cloudwatch as:
where the query is simply the url-encode of match[]={__name__=~"candies.*"}.
While this workaround seems to work, it makes the code not very readable and a bit hard to maintain, so perhaps this feature could be integrated directly into the code?
If you think it's a good idea to include the feature I might be able to open a PR for it.
Thank you for your feedback.
The text was updated successfully, but these errors were encountered:
First of all hello and thank you very much for sharing this very cool project!
I think it would be nice to support the ability to fetch metrics held in the Prometheus server which are not usually exposed any other way. For instance
alerts
andrecording rules
.I have found a workaround for this use case, if anyone is interested, to scrape the
/federate
endpoint and passing the correct "instant vector selector" and url-encoding the query.For instance, let's say that your metric is named
candies
(could be a recording rule aggregating and manipulating other primitive metrics), then you can invokeprometheus-to-cloudwatch
as:where the query is simply the url-encode of
match[]={__name__=~"candies.*"}
.While this workaround seems to work, it makes the code not very readable and a bit hard to maintain, so perhaps this feature could be integrated directly into the code?
If you think it's a good idea to include the feature I might be able to open a PR for it.
Thank you for your feedback.
The text was updated successfully, but these errors were encountered: