Skip to content
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

[2.x] Fix documentation bugs #1507

Merged
merged 1 commit into from
Sep 1, 2023
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
3 changes: 2 additions & 1 deletion docs/logs.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -6,14 +6,15 @@ The agent will automaticaly inject correlation IDs that allow navigation between

This features is part of {observability-guide}/application-logs.html[Application log ingestion strategies].

The {ecs-logging-go-ref}/intro.html[`ecs-logging-go`] library can also be used to use the {ecs-logging-ref}/intro.html[ECS logging] format without an APM agent.
The {ecs-logging-go-logrus-ref}/intro.html[`ecslogrus`] and {ecs-logging-go-zap-ref}/intro.html[`ecszap`] libraries can also be used to use the {ecs-logging-ref}/intro.html[ECS logging] format without an APM agent.
When deployed with the Go APM agent, the agent will provide <<log-correlation-ids,log correlation>> IDs.

The Go agent provides integrations for popular logging frameworks that
inject trace ID fields into the application's log records. You can find a list of
the supported logging frameworks under <<supported-tech-logging, supported technologies>>.

If your favorite logging framework is not already supported, there are two other options:

* Open a feature request, or contribute code, for additional support as described in <<contributing>>.
* Manually inject trace IDs into log records, as described below in <<log-correlation-manual>>.

Expand Down
Loading