Possible to have all rules visible from Promxy? #706
Replies: 1 comment
-
This is partially true. Promxy can aggregate responses from multiple downstream prometheus APIs -- but it cannot do its own metrics scraping (promxy has no TSDB internally).
Today the So if we wanted to show the downstream targets/rules this would require merging logic for all of the rules/targets/alerts -- which may be more complicated than helpful? Also this would be a "breaking change" as today promxy only shows those for "itself" instead of a merge of downstream. Not opposed to doing this necessarily, but definitely would need some better vision of how we'd do that and a use-case that would want that level of consolidation.
If you add scrape configs they will be ignored by promxy as it doesn't have the scrape stuff wired up. |
Beta Was this translation helpful? Give feedback.
-
Hello, we have 2 Prometheus servers and Promxy configured to have them as server_group and it does well regarding querying.. but when we go do Promxy UI we see that all rules/targets/alerts are empty and as I understand Promxy can act as prometheus itself if we add rules for it... but we wonder is there anyway, any use case just to have Promxy UI show original targets/alerts/recording rules? what is the best approach to do it? for example if we add scraping configs to Promxy then what? it will also try to do scraping?
Beta Was this translation helpful? Give feedback.
All reactions