### MetricsHub
MetricsHub 1.0.00

Home
- Troubleshooting

# No Data in the Observability Platform

Missing data in your observability platform often indicates an issue with telemetry data transmission, likely caused by a misconfiguration at the exporter level.

The troubleshooting steps vary depending on your edition of MetricsHub.

## MetricsHub Community

1. Enable logging[1]

2. Check the resource logs (`metricshub-agent-$resourceId-$timestamp.log`) and connector logs for potential issues, such as:

   - Misconfigured endpoints (e.g., incorrect hostnames)
   - Authentication failures (e.g., incorrect credentials).

## MetricsHub Enterprise

1. Enable logging for the MetricsHub Agent[1] and the OTel Collector[2]

2. Check the resource logs (`metricshub-agent-$resourceId-$timestamp.log`) for any errors or anomalies

3. Review the OpenTelemetry Collector logs (`otelcol-$timestamp.log`) to ensure the following:

   - the MetricsHub Agent successfully launched the OpenTelemetry Collector
   - Exporters and processors properly started
   - No connection issues or authentication failures with the configured observability platform(s) (Datadog, BMC Helix, Prometheus, Grafana, etc.).

Refer to What to look for in otelcol-$timestamp.log[3] for more details.

data observability platforms troubleshooting monitoring observability opentelemetry otel
Links:

- [1] ./metricshub-logs.html
- [2] ./otel-logs.html
- [3] ./otel-logs#what-to-look-for-in-otelcol-timestamplog

## Search Results for {{siteSearch | truncate:'50'}}

{{resultArray.length}}
{{parent.title}} {{parent.title}}

{{result.title}}

{{result.body | truncate:'400'}}

{{parent.title}}
{{result.title}}
{{result.body | truncate:'100'}}

No results.