Troubleshooting Service Catalog

문서 > Datadog 서비스 카탈로그 > Troubleshooting and Best Practices Guides > Troubleshooting Service Catalog

이 페이지는 아직 한국어로 제공되지 않으며 번역 작업 중입니다. 번역에 관한 질문이나 의견이 있으시면 언제든지 저희에게 연락해 주십시오.

APM-instrumented services not appearing

If services that you know are instrumented for APM are not appearing in the Service Catalog list, it’s likely because they have not been emitting performance data in the past hour for the selected env (or any Primary Tag values of your choosing) or Secondary Primary Tag. To confirm, on the Performance tab, hover over the columns where you expect the performance metrics to appear and see information on which environments the services are active.

Hover message indicating that no performance data has been reported in the past hour

SLOs not listed in Setup Guidance section

The count in the Service Catalog Setup Guidance section reflects the number of SLOs with service tags. If your SLOs are not listed, verify that they have service tag values specified and that they match with the service names in other products such as APM and USM.

Additional telemetry is available to a service but it’s not listed

Service Catalog relies on the DD_SERVICE tag in all telemetry types (infrastructure metrics, logs, network performance monitoring) to gather information about a given service. If you don’t see a telemetry type that you expect in the Service Catalog, ensure that you have configured the DD_SERVICE tag according to the instructions in Unified Service Tagging.

Can’t add metadata for RUM services

Adding metadata for RUM services is not supported.

If you have many services that share the same metadata, you do not need separate service.datadog.yaml files for each one. You can define multiple services in a single service.datadog.yaml file by separating each service with a --- separator. Copy and paste the shared metadata for the relevant dd-service entities.