Understanding Your Service Configuration
Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel,
n'hésitez pas à nous contacter.
Following monitoring best practices such as tracing, logging, and code profiling helps you ensure that you have all the data you need during incident triage. Service Catalog provides automatic checks for these recommended setups. It helps you detect any monitoring gaps and helps you connect all available data for a service.
To view the configuration completeness for a service, click it in the Service Catalog. On the service details page, click Service Info in the upper-right side.
On this page you can see the ownership, PagerDuty, and related links information you’ve specified for the service in its service definition.
You can also find which Datadog features you are actively using for a given service, to help you find and close gaps in your monitoring completeness.
This table does not necessarily reflect billing for individual products, but rather activity for the service you are presently examining. For example, if the service does not emit infrastructure metrics for a long time, Infrastructure Monitoring might have Not Enabled specified, even if you have hosts or containers running infrastructure monitoring.
Further reading
Documentation, liens et articles supplémentaires utiles:
