rmarops

ran into this issue, and this helped me solve it. good candidate for documentation tag?

at the time the old 1.15 version -- i was in middle of reverting an app after having the grace period issues with 1.21.1

Reproduced by extracting and running prometheus locally on the opensearch host, confirmed `curl localhost:9090/metrics` produced metrics then attempted from devtools: ``` POST _plugins/_query/_datasources { "name" : "prometheus", "connector": "prometheus", "properties"...

Am I understanding correctly that this requires running `copilot env init --import-cert-arns arn:aws:acm:us-east-1...` which means you have to create a fresh env?

hey @Lou1415926, I've tried this but im not sure if i am missing a step https://github.com/aws/copilot-cli/discussions/5474

I'd like to see read only user for end users and operators to have visibility to any monitors created by admin.

Option 3 does not work me against Amazon Linux 2023 and pssh using a SHA-256 rsa key. Same key used outside of pssh from command line works fine. For the...

adding the screenshot of query workbench working with mongodb_up metric 

just confirmed that all node_exporter (node*) metrics are not available as well

I believe the question and answer here is related to the issue https://stackoverflow.com/questions/68081062/prometheus-not-expose-all-collected-metrics Excerpt screenshots   I can confirm the metrics URL only lists prometheus* and go* metrics whereas...