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.

Sign up for GitHub

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

[doc] showing how to use a custom logger #136

Merged
merged 2 commits into from
Jun 9, 2017
Merged

[doc] showing how to use a custom logger #136

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8d591a2
[doc] showing how to use a custom logger
ufoot Jun 9, 2017
3dbe8f8
[doc] rewrote example using a custom logger that writes to a file
ufoot Jun 9, 2017
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
14 changes: 14 additions & 0 deletions docs/GettingStarted.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -479,6 +479,20 @@ for the first time:
Remember that the debug mode may affect your application performance and so it must not be used
in a production environment.

### Using a custom logger

By default, all logs are processed by the default Ruby logger.
Typically, when using Rails, you should see the messages in your application log file.
Datadog client log messages are marked with ``[ddtrace]`` so you should be able
to isolate them from other messages.

Additionally, it is possible to override the default logger and replace it by a
custom one. This is done using the ``log`` attribute of the tracer.

f = File.new("my-custom.log", "w+") # Log messages should go there
Datadog::Tracer.log = Logger.new(f) # Overriding the default tracer
Datadog::Tracer.log.info { "this is typically called by tracing code" }

### Environment and tags

By default, the trace agent (not this library, but the program running in
Expand Down