Navigate the Service Catalog
On the Service Catalog page, see the list of services in your Datadog organization which are either detected from collected data or manually declared by someone registering the service. To find a particular service, search by its name. To narrow down to only explicitly declared entries, you can search by the Service Origin facet and filter by user-defined.
Ownership view
In the Ownership tab, you can click the icons in the Contact and Repo columns and be directed to the tools and projects specified in the service definition. For example, you can access the owning team’s Slack channel or GitHub repository containing the service code.
The Telemetry column displays what types of telemetry data Datadog is collecting for the service. Clicking on the icons directs you into the corresponding Datadog product view. For example, the Agent sends traces to Datadog, and you can click the Traces icon to view them in APM.
Sort the table by Team or On Call columns to see which services each team is responsible for, and identify services where ownership and responsibility are not specified yet.
Reliability view
The Reliability tab contains information about the stability of your services. Sort the table by clicking on columns in the list to reveal:
- Which services deployed most recently, or have not deployed for a long time.
- Which services are reporting the most errors, and whether they are new issues.
- Which services have ongoing incidents.
- Which services have monitors that are triggered.
Click the Settings icon on the right hand corner to hide columns from the list.
The Performance tab provides several ways to view how your services are performing and what needs the most attention.
The environment dropdown works as a filter. For example, when you select env:prod, the list displays only services that have performance data (APM/USM telemetry) in env:prod during the last hour. When you select env:*, you can see all environments where a service emits telemetry at a glance, and expand to see detailed performance metrics per environment.
The second dropdown allows you to rescope any APM data you have in the Performance view to the second primary tag on APM trace metrics. This dropdown does not affect how many services you see in the list. RUM applications are not associated with specific environments (unlike APM or USM), and are only viewable when you select the env* option in the environment dropdown.
You can change the default environment in APM > Setup & Configuration > Settings.
The performance metrics are tied to services’ primary operations. If a service is only detected by APM, the performance view shows the APM trace metrics. If a service is only detected by USM, the performance view shows the USM metrics. If a service is detected by USM and APM, the performance view shows the Trace Metrics instead of USM metrics.
Sort the table by clicking columns to reveal services that:
- Deployed most recently, or have not deployed for a long time
- Are receiving the most requests per second, or are not receiving any traffic
- Have the highest latency at various percentiles
- Have the highest error numbers or rates
- Are running on the most pods, hosts, or serverless environments
- Have related dashboards where you can see more performance data breakdowns, and identify which ones need to have dashboards added to their service definition
- Have the highest or lowest Apdex scores
- Have monitors that are triggered
Click the Settings icon on the right hand corner to hide metric columns from the list.
Security view
The Security tab provides several ways to assess and improve the security posture of your services. This includes understanding the number and severity of known security vulnerabilities in the open source libraries, and viewing how your services are targeted by attackers. Sort the table by clicking columns to reveal services that:
- Expose known security vulnerabilities, including the individual severities.
- Are receiving the most attack attempts.
- Are targeted by the most attackers.
- Have the most severe threats, where the services are impacted by the attacks.
- Are monitored and protected by Application Security Management
To access additional details describing security vulnerabilities and signals, click on the service row to open a detailed side panel. Alternatively, click on the pop-over View Service Details button, which opens the service page, and in turn, its security tab.
Click the Settings icon on the right hand corner to hide metric columns from the list.
Costs view
The Costs tab provides several ways to understand the costs associated with your services. Powered by Cloud Cost Management, you can identify potential inefficiencies, saving opportunities, and change over time. Positioning costs data alongside metrics available in Service Catalog can improve visibility into how engineering changes affect overall cloud spend. Sort the table by clicking columns to reveal services that:
- Have the highest amortized AWS costs in the last month
- Show a significant change in the rate of cloud spending over time
For more information on a service’s cost changes, click on the service row to open a detailed side panel. To see this information on the Cloud Costs page, click the View in Analytics button.
This information is only available for Cloud Cost Management customers who have configured the necessary AWS Integration and Tag Pipelines.
Click the Settings icon on the right hand corner to hide metric columns from the list.
Software Delivery View
The Software Delivery tab provides several ways to assess and improve the pre-production status of your services. This includes understanding the status of your CI pipelines and viewing your static analysis violations. You can:
- View performance of the CI pipelines related to your services.
- Find security and code quality issues from Static Analysis.
- Easily pivot from Service Catalog to troubleshoot pre-production slowdowns and failures.
To access additional details describing your CI status and static analysis violations, click on a service and see the status of each pipeline and rule violation.
Further reading
Additional helpful documentation, links, and articles:
