Discovering Endpoints from APM

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

Overview

If a service has a supported tracer installed, the API Catalog is automatically populated with all endpoints discovered from this service.

To check for compatibility issues, click Learn More in the app, then select Troubleshoot.

ALT TEXT

Providing endpoint paths manually

Add the datadog.api_catalog.route tag to force endpoint discovery by the API Catalog. This tag should contain the matched route, that is, the path template in the format used by the respective server framework.

API Catalog filters out spans that do not contain the following tags:
  • http.method
  • http.status_code

Example

The following examples demonstrate adding a span tag for each using custom instrumentation:

Java

span.setTag("datadog.api_catalog.route", "/products/{productId}")

Python

span.set_tag("datadog.api_catalog.route", "/products/{productId}")

.NET

scope.Span.SetTag("datadog.api_catalog.route", "/products/{productid}");

Go

span.SetTag("datadog.api_catalog.route", "/products/:id")

Ruby

Datadog::Tracing.active_trace.set_tag('datadog.api_catalog.route', '/products/:id')

After you set this tag, you should see this tag in spans:

ALT TEXT

This leads to the endpoint displaying in the API Catalog:

ALT TEXT

Further reading

추가 유용한 문서, 링크 및 기사:

Datadog API CatalogDOCUMENTATION more more