SpringBoot集成Datadog：Hikaricp、Tomcat及JDBC指标未导出求助

Hey there! I’ve run into this exact issue before with Spring Boot 2.x and Micrometer’s Datadog registry—let’s walk through why those metrics are showing up in /actuator/metrics but not making it to Datadog, and how to fix it.

1. First: Align Your Micrometer Version with Spring Boot #

Using latest.release for micrometer-registry-datadog is a common pitfall here. Spring Boot 2.3.3.RELEASE is tied to Micrometer 1.5.6, but newer Datadog registry versions (2.x+) require Micrometer 1.6+ or higher. This version mismatch can cause silent failures in metric export without throwing obvious errors.

Update your dependency to use the version matched to your Spring Boot release:

implementation 'io.micrometer:micrometer-registry-datadog:1.5.6'

You can confirm the correct Micrometer version for your Spring Boot build by checking Spring Boot’s official dependency documentation.

2. Explicitly Whitelist Missing Metric Prefixes #

The Datadog registry filters out some metrics by default—even though your app is collecting them (as confirmed by /actuator/metrics), they aren’t being sent to Datadog unless you explicitly include them.

Add this configuration to your application.yml (or equivalent .properties file) to whitelist the HikariCP, Tomcat, and JDBC metrics:

management:
  metrics:
    export:
      datadog:
        api-key: YOUR_DATADOG_API_KEY
        # Include the missing metric prefixes + keep your existing 60 metrics
        include: "*hikaricp*,*tomcat*,*jdbc*,*"
        # Optional: Add a tag to easily identify your app in Datadog
        tags:
          application: YOUR_APP_NAME
    # Optional: Double-check metric collection is enabled at the source
    enable:
      hikaricp: true
      tomcat: true
      jdbc: true
  endpoints:
    web:
      exposure:
        include: metrics,health # Confirm actuator endpoints are accessible

The * wildcards ensure you don’t lose your existing metrics while adding the missing ones.

3. Verify Metric Naming & Datadog Ingestion #

Micrometer converts metric names to Datadog’s format automatically, but sometimes they might show up under slightly different labels. For example:

• HikariCP metrics like hikaricp.connections.active in Micrometer will appear as hikaricp.connections.active in Datadog
• Tomcat metrics might have prefixes like tomcat.servlet.requests or tomcat.global.requests

After updating your config and restarting the app, wait 5-10 minutes, then search Datadog’s metrics explorer for these prefixes to confirm they’re arriving.

4. Debug Silent Connection/Export Issues #

If metrics still don’t show up, check if your app can reach Datadog’s API endpoint (https://api.datadoghq.com). You can enable debug logging for Micrometer to catch export errors:

logging:
  level:
    io.micrometer.datadog: DEBUG

Look for logs mentioning failed requests or authentication problems—this usually points to an invalid API key or network access issues.

内容的提问来源于stack exchange，提问作者Suresh Naik