Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Amazon Managed Service for Prometheus DataSource not recognized when importing #2480

Open
tomisanhues2 opened this issue Aug 20, 2024 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/support Categorizes issue or PR as a support question. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@tomisanhues2
Copy link

What happened:

When attempting to import the kube-state-metrics-v2 it cannot find a correctly configured and working prometheus datasource if it used Amazon Managed Service for Prometheus datasource

What you expected to happen:

Not sure if this is a bug or a limitation.

How to reproduce it (as minimally and precisely as possible):

n/a

Anything else we need to know?:

If there is a workaround to adding AWS Managed Prometheus datasource without the Amazon Managed Service for Prometheus plugin by GrafanaLabs would be much appreciated, Given the SigV4 Auth it was recommended to use the plugin.

@tomisanhues2 tomisanhues2 added the kind/bug Categorizes issue or PR as related to a bug. label Aug 20, 2024
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Aug 20, 2024
@logicalhan
Copy link
Member

/kind support
/triage accepted

@k8s-ci-robot k8s-ci-robot added kind/support Categorizes issue or PR as a support question. triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/support Categorizes issue or PR as a support question. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants