Skip to content

docs: fix link #1631

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 20, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/usage/service.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -39,9 +39,9 @@ An example for this use case is a log entry being recorded for a particular serv
[[ecs-service-usage-origin-target]]
====== Describing external services in an invocation relationship

Multiple services can be in an invocation relationship.
Where it is possible to apply https://www.elastic.co/guide/en/apm/get-started/master/distributed-tracing.html[distributed tracing] on all the involved services
describe the individual services <<ecs-service-usage-service-at-root,using root-level service fields>>
Multiple services can be in an invocation relationship.
Where it is possible to apply https://www.elastic.co/guide/en/apm/guide/current/apm-distributed-tracing.html[distributed tracing] on all the involved services
describe the individual services <<ecs-service-usage-service-at-root,using root-level service fields>>
and use the <<ecs-related,tracing fields>> to represent the invocation relationship.

There are situations when distributed tracing cannot be applied on some external services that are in an invocation relationship to an observed service.
Expand Down