You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/tracing/services/service_page.md
+11-3Lines changed: 11 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ Selecting a service on the Software Catalog leads you to the detailed service pa
33
33
34
34
Consult on this page:
35
35
36
-
*[Service health](#service-health)
36
+
*[Service health](#service-health)
37
37
*[Service monitor states](#service-monitor)
38
38
*[Watchdog Insights](#watchdog-insights)
39
39
*[Summary cards](#summary-cards)
@@ -57,7 +57,7 @@ Service health is available in several places in Datadog:
57
57
58
58
1.[Software Catalog][23]
59
59
2. Service pages
60
-
3. Service dependendency maps, if Watchdog detects that an issue spans multiple service dependencies.
60
+
3. Service dependendency maps, if Watchdog detects that an issue spans multiple service dependencies.
61
61
4. Service pills
62
62
63
63
Service health displays the status of your service as *Critical* or *Warning* if at least one of the following conditions is met:
@@ -113,7 +113,7 @@ On the upper-right corner of each graph click on the arrow in order to export yo
113
113
114
114
## Resources
115
115
116
-
See Requests, Latency, and Error graphs broken down by resource to identify problematic resources. Resources are particular actions for your services (typically individual endpoints or queries).
116
+
See Requests, Latency, and Error graphs broken down by resource to identify problematic resources. Resources are particular actions for your services (typically individual endpoints or queries).
117
117
118
118
Below, there's a list of [resources][11] associated with your service. Note: If the resource represents an external interface of an HTTP service, the list displays endpoints instead.
{{< img src="profiler/apm_service_page_pivot_to_contention_comparison_1.mp4" alt="Pivoting from APM service page to Profiling comparison page to find the line of code causing latency" video=true >}}
242
242
243
+
### Memory Leaks
244
+
If you set up the [Continuous Profiler][15] and the service is running in a containerized environment, the [Memory Leaks][24] tab becomes available.
245
+
246
+
It guides you through a workflow for identifying potential memory leaks and shows the most actionable data.
View the list of traces associated with the service in the traces tab, which is already filtered on your service, environment, and operation name. Drill down to problematic spans using core [facets][16] such as status, resource, and error type. For more information, click a span to view a flame graph of its trace and more details.
245
252
@@ -281,3 +288,4 @@ Visualize the cost associate with your service's infrastructure used in the Cost
0 commit comments