When troubleshooting your Infrastructure agent, generate
verbose logs for a few minutes to find and investigate errors. This can be useful for your own troubleshooting or when working with New Relic Support.
Verbose logging generates a lot of data very quickly. When finished generating logs, be sure to set
verbose: 0 to reduce disk space consumption.
verbose log files requires editing your configuration file; for a sample config file that includes all applicable settings, see the example template. To generate detailed logs:
|2.||Let your host run at normal load for about three minutes to generate sufficient logging data.|
Return your settings to default:
Examine the log file for errors.
If you need to send your log file to New Relic Support:
Notes for specific systems
These are some additional notes and requirements for specific systems, used to supplement the general logging instructions:
- Containerized agent on CoreOS
If you are using a containerized Infrastructure agent on CoreOS:
Choose one of these options to change the log level to verbose:
Recommended: Set the environment variable
1. Running this on the command line would look like:
You can also edit the config file to set
verbose: 1. However, editing the config file in a container is not recommended because it requires rebuilding the image twice: once to add verbose logging and once to remove it.
Use journalctl to collect the logs:
journalctl -u newrelic-infra > newrelic-infra.log
- Set the verbose logging level back to
0after collecting logs for a few minutes.