Every New Relic agent includes strong safeguards to ensure data security. For example, New Relic automatically encrypts sensitive information before it is transmitted. For more information about New Relic's security measures, see our security and privacy documentation, or visit the New Relic security website.
If you need to record and view information about all data your app transmits to New Relic, you can enable audit logging for short periods of time. This is useful, for example, with debugging or auditing, when you need detailed information about what exactly is being transmitted.
Be sure to disable audit logging as soon as you are finished using it. This feature causes additional overhead, which may overload the audit log file if left turned on for extended periods of time.
APM agent audit logging
For details about the audit logging options for your APM agent's configuration file, see the agent-specific documentation:
When starting the C SDK daemon, add
./newrelic-daemon -f -logfile stdout -loglevel debug -auditlog audit.log
|Go||Logging is optional with the Go agent. If you are using
|Node.js||New Relic's Node.js agent does not use separate audit logs because the payload is already available in the configuration logs. To view increasing levels of detail, use your config file's logging
Infrastructure agent logging
You can generate infrastructure monitoring logs for troubleshooting our infrastructure agent.