prometheus integration to use PrivateLink
There is a possibility to integrate Prometheus into an Atlas project.
However, for enabling this integration, one needs to add Prometheus's IP address in the IP Access List.
This procedure has 2 flaws in it:
1. Prometheus runs as pods on some use-cases, meaning that its IP is ephemeral.
2. For projects that work solely with PrivateLink enabled and no open IP in the IP Access List, one cannot use the Prometheus integration (already talked with support about that).
The improvement here is to add the Prometheus integration to work as well in "PrivateLink-only" mode.
Amit
shared this idea
-
Calvin
commented
Important metrics, but shouldn't require a public IP whitelist and be sent over the internet.
-
Siu Lun, Alan
commented
we need private endpoint too to provide more secure connection with metrics monitoring capabilities
-
Christian
commented
We need with private peering too
-
Mark
commented
For enterprise customers, this feature is a must.
-
Fulton
commented
VPC Native as well.
Would need a Private Link, VPC Native, and Public discovery endpoints. Or maybe some sort of scrape parameter to add to the request...
-
M
commented
We would like to use the prometheus integration but are hitting the same limitation since we reach our clusters via privatelink only
-
Daniel
commented
As we have security policies to only allow access to Mongo cluster over private endpoints we also need to have the possibilty to scrape the metrics that way.
Optionally, if we can limit network access to only allow the prometheus port over internet it could work as well.
-
Valentin
commented
Similar request. We need with private peering.