Service is the only component type in Service Catalog schema versions v2, v2.1, and v2.2. v3.0 and above supports multiple kinds of components, including kind:system, kind:service, kind:queue, kind:api, and kind:datastore.

Assigning an owner

You can assign a team to entries in the Service Catalog either in the UI or by creating a Service Definition. Datadog recommends that you set up Datadog Teams so that you can specify individual members of the team and take advantage of Teams filters across common views like Dashboards and Notebook lists.

Determining and communicating criticality

Not all instances of observability carry the same level of importance. Some are mission-critical, while others are less so. By identifying the service tier, lifecycle, and the application ecosystem they belong to, you can determine if the observability coverage is adequate and quickly assess the severity of issues.

Understanding your service configuration

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 the service in the Service Catalog, then find the Setup Guidance tab:

Alternatively, on the Service page, click Service Config on the lower-left side:

In the Setup Guidance section, 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 Detected specified, even if you have hosts or containers running infrastructure monitoring.

Investigating infrastructure

From the Performance tab, find the service you are investigating. In the Infrastructure column, click the resources related to this service to View in Service Context Map.

The Service Context Map provides an overview of the relationships and dependencies between services and related infrastructure. Use this view to analyze the source of an issue by looking at upstream and downstream services and infrastructure.

Click a service in Service Catalog to open the side panel with the following details:

Service details by views

• Ownership information from the Service Definition, such as links to team, contacts, source code, and supplemental information like documentation and dashboards.
• Reliability information including deployment status, SLOs, ongoing incidents, and error information.
• Performance graphs showing requests, errors, latency, and time spent by downstream services.
• Security information including known vulnerabilities exposed in the service’s libraries, the timeline and type of attacks, identity of attackers, and security threats impacting your services.
• Costs information showing the cloud spend for a service, broken down by resource types.
• Pre-production information regarding your software delivery process, such as the average build duration and success rate of CI pipelines related to your service, along with static analysis results from CI.

Configuration details

• Setup completeness status for Datadog products that can collect data for the service.

• External libraries used which includes the ability to download the Inventory of Libraries.

• Service definition in YAML with a link to the service’s source code.

• An interactive service map displaying services upstream and downstream from this service.

• Defined and Related Dashboards showing a list of pre-defined and Watchdog recommended dashboards when available.

• Service Scorecards showing a snapshot of the service’s scores and last evaluation timestamp.

• Active library configuration for Java and .NET services with the latest Agent configured with Remote Configuration enabled, you can adjust the trace sampling rate (from 0.0 to 1.0), enable Log Injection to correlate traces and logs data, and specify HTTP header tags to be applied to all traces coming into Datadog from this service. In the Setup Guidance tab, beside Active Library Configuration, click Edit to change these settings and immediately apply them without restarting the service.

Click View Related and select a page from the dropdown menu to navigate into related pages in Datadog, such as the APM Service Page and service map for this service, or related telemetry data pages, such as for distributed tracing, infrastructure, network performance, Log Management, RUM, and Continuous Profiler.

Further reading

お役に立つドキュメント、リンクや記事:

Registering Services with the Service Definition APIDOCUMENTATION See Upstream and Downstream Dependencies During an Active IncidentGUIDE Manage Service Catalog entries with the Service Definition JSON SchemaBLOG Gain visibility into risks, vulnerabilities, and attacks with APM Security ViewBLOG Easily add tags and metadata to your services using the simplified Service Catalog setupBLOG I use GitHub Actions for Data­dog's Service Catalog, and you should, tooBLOG Datadog Service CatalogDOCUMENTATION