Tyk will log of it’s output to
stdout, in a typical installation, these will be handled or redirected by the service manager running the process, and depending on the Linux Distribution, will either be output to
Log data is usually of the Error level and higher, though you can enable debug mode reporting by adding the
--debug flag to the process run command (Warning, this generates a lot of output and is not recommended).
Tyk will try to output structured logs, and so will include context data around request errors where possible.
1.1.Aggregated logs with Sentry
Tyk’s logger supports multiple back-ends, the one that currently ships with Tyk is the Sentry hook, this makes it possible to send log data from multiple Tyk processes to a sentry server in order to monitor the context around HTTP errors and other notifications that Tyk makes.
To enable Sentry as a log aggregator, update these setting sin both your
tyk.conf and your
Set this to true to enable the sentry logger, you must specify a sentry DSN under
The Sentry-assigned DSN (a kind of URL endpoint) that Tyk can send log data to