MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Add new feedback Subscribe
116 VOTE
Status Submitted
Categories Atlas Monitoring, Alerts & Observability
Created by Guest
Created on Mar 15, 2022

RELATED FEEDBACK

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.
  • Guest
    Aug 19, 2025
    It's highly needed feature for us. Any update on topic?
    Reply
  • Guest
    Apr 16, 2025
    This is a critical feature for a high profile customer. Any updates on the feature request pipeline?
    Reply
  • Guest
    Apr 4, 2025
    Hello. Also interested by the exact same feature. Any news on the subject?
    Reply
  • Guest
    Oct 31, 2024
    Hi. The feature request was created in March 2022. Are there any plans from the team to implement it in the near future?
    Reply
  • Guest
    Mar 13, 2024
    > Currently there is needed public egress - and this can be issue in fully private clouds, where all public traffic is blocked. I do agree. A generic solution would be to expose the Admin API as a private endpoint through VPC peering. I think I saw such a feature request already.
    Reply
  • Guest
    Mar 13, 2024
    Hi, already using targetScheme=PRIVATE. But full private integration means, that also the endpoint for Prometheus Http Service Discovery should be exposed in private network (where mongo cluster and target for service discovery are exposed). Currently there is needed public egress - and this can be issue in fully private clouds, where all public traffic is blocked. Thanks
    Reply
  • Guest
    Mar 12, 2024
    This is already supported. Scrape configs do support a so-called target scheme: `https://cloud.mongodb.com/prometheus/v1.0/groups/GROUP-ID/discovery?targetScheme=PRIVATE"` This will return a scrape config referencing the metric endpoint using a private FQDN of the cluster node you want to receive metrics from. This works for VPCpeering-enabled Atlas projects, but regarding AWS PrivateLink your miles may vary.
    Reply
  • Guest
    Jan 1, 2024
    due to security policies access to the Mongo cluster is allowed only over private endpoints, we need the same way for fetching metrics.
    Reply
  • Guest
    Jul 11, 2023
    Important metrics, but shouldn't require a public IP whitelist and be sent over the internet.
    Reply
  • Guest
    Mar 28, 2023
    we need private endpoint too to provide more secure connection with metrics monitoring capabilities
    Reply
  • Guest
    Feb 27, 2023
    We need with private peering too
    Reply
  • Guest
    Nov 15, 2022
    For enterprise customers, this feature is a must.
    Reply
  • Guest
    Nov 9, 2022
    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...
    Reply
  • Guest
    Oct 20, 2022
    We would like to use the prometheus integration but are hitting the same limitation since we reach our clusters via privatelink only
    Reply
  • Guest
    Aug 26, 2022
    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.
    Reply
  • Guest
    May 2, 2022
    Similar request. We need with private peering.
    Reply
  • +16