This may be because the built-in service discovery feature of Managed Service for Prometheus automatically collects metrics from your applications, which can cause additional fees.
What triggers the extra charges
When you connect an application to Managed Service for Prometheus, default service discovery is automatically enabled and begins collecting metrics immediately, even if you did not explicitly configure it.
Managed Service for Prometheus supports four types of service discovery:
| Type | How it starts | Action required |
|---|---|---|
| Default service discovery | Enabled automatically when you connect an application | None -- starts automatically |
| ServiceMonitor | Requires manual setup | Add and configure a ServiceMonitor |
| PodMonitor | Requires manual setup | Add and configure a PodMonitor |
| Custom service discovery | Requires manual setup | Add and configure custom rules |
Each active service discovery collects metrics based on its configuration, which may cause additional fees.
How to stop the extra charges
Disable the service discovery rules you do not need. The steps vary by instance type:
Prometheus instance for Container Service -- See Manage service discoveries.
Prometheus instance for ECS -- See Manage ECS service discovery.
Review the collected metrics before you disable a service discovery rule. Keep the metrics that provide visibility into critical services, and disable only the ones you do not need.