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
Is your feature request related to a problem? Please describe.
When configuring a Amazon Managed Service for Prometheus data source we are asked to select the Prometheus type, and when Cortex is selected the relevant version too. Both of these fields seem unnecessary for the scope of this data source.
Describe the solution you'd like
This plugin should use the correct Prometheus type and Cortex version that best matches AMP, without users having to select the details themselves.
Additional context
I understand AMP is running Cortex
I am not aware of the version of Cortex being used by AMP
The text was updated successfully, but these errors were encountered:
Hi @sjparkinson - thanks for pointing this out. That configuration section appears to be left over from when this plugin was split off from the core Prometheus datasource, and is in fact unnecessary. We'll clean that up. In the mean time, you don't actually have to select anything in those fields, you can just leave the placeholders and it will work just fine.
Is your feature request related to a problem? Please describe.
When configuring a Amazon Managed Service for Prometheus data source we are asked to select the Prometheus type, and when Cortex is selected the relevant version too. Both of these fields seem unnecessary for the scope of this data source.
Describe the solution you'd like
This plugin should use the correct Prometheus type and Cortex version that best matches AMP, without users having to select the details themselves.
Additional context
The text was updated successfully, but these errors were encountered: