All Products
Search
Document Center

Application Real-Time Monitoring Service:Report metrics with OpenTelemetry endpoints

Last Updated:May 07, 2026

Managed Service for Prometheus provides OpenTelemetry endpoints to ingest metrics from your OpenTelemetry-instrumented applications into Managed Service for Prometheus. You can then use Grafana to query this data to monitor the performance and health of your applications.

Usage notes

  • Only V1 Prometheus instances are supported.

  • OpenTelemetry metrics can be reported only over HTTP. gRPC is not supported.

  • When you report data over HTTP, the Content-Encoding header supports only the application/protobuf serialization method. The application/json serialization method is not supported.

  • The following table shows the mapping between OpenTelemetry and Prometheus metric types.

    OpenTelemetry

    Prometheus

    Sum(monotonic & cumulative)

    counter

    Sum(monotonic & delta)

    gauge

    Sum(none-monotonic & cumulative)

    gauge

    Gauge

    gauge

    Histogram(cumulative)

    histogram

    Histogram(delta)

    Not supported

    Exponential Histogram

    Not supported

    Summary

    summary

  • Supported regions:

    Area

    Region

    Region ID

    Chinese mainland

    China (Hangzhou)

    cn-hangzhou

    China (Shanghai)

    cn-shanghai

    China (Shenzhen)

    cn-shenzhen

    China (Heyuan)

    cn-heyuan

    China (Guangzhou)

    cn-guangzhou

    China (Qingdao)

    cn-qingdao

    China (Beijing)

    cn-beijing

    China (Zhangjiakou)

    cn-zhangjiakou

    China (Hohhot)

    cn-huhehaote

    China (Ulanqab)

    cn-wulanchabu

    China (Chengdu)

    cn-chengdu

    China (Hong Kong)

    cn-hongkong

    International

    Singapore

    ap-southeast-1

Prerequisites

You have created a Prometheus instance. For more information, see:

Step 1: Get the OpenTelemetry endpoint

  1. Log on to the Cloud Monitor console. In the left navigation pane, choose Managed Service for Prometheus > Instances. The Instances page appears.

  2. At the top of the page, select the region where your instance is located. Find the target instance and click Settings in the Actions column.

  3. On the Settings tab, copy the public or internal endpoint, as needed.

    image.png

Step 2: Update the application endpoint

This topic uses Java as an example. In OtlpHttpMetricExporterBuilder, update the Endpoint parameter with the endpoint from Step 1 to ingest your application's OpenTelemetry metrics into Managed Service for Prometheus. For more information, see the sample demo.

You can also configure the following parameters:

  • By default, compression is disabled for OpenTelemetry clients. To reduce network usage, set the compression parameter to gzip.

  • To prefix all metrics reported to Managed Service for Prometheus, add a header that sets the metricNamespace.

  • By default, the service adds an OpenTelemetry scope label to all metrics reported to Managed Service for Prometheus. To prevent this, add a header that sets skipGlobalLabel to true.

Note

For more information about how to configure these parameters, see the sample demo.

Step 3: View monitoring data

  1. Log on to the Cloud Monitor console. In the left navigation pane, choose Managed Service for Prometheus > Instances. The Instances page appears.

  2. Click the name of the target instance.

  3. Click Metric Management. On the Explore tab, enter a PromQL query that includes your metrics to view the reported data.