The New Relic Go agent default security settings automatically provide security for your APM data to ensure data privacy and to limit the kind of information New Relic receives. You may have business reasons to change these settings.
If you want to restrict the information that New Relic receives, you can enable high-security mode. If high-security mode or the default settings do not work for your business needs, you can apply custom settings.
For more information about New Relic's security measures, see our security and privacy documentation, or visit the New Relic security website.
Default security settings
By default, here is how the New Relic Go agent handles the following potentially sensitive data:
- Request parameters: The agent does not capture HTTP request parameters.
- HTTPS: The agent communicates with New Relic using HTTPS.
High-security mode settings
When you enable high-security mode, the default security settings are locked so that users cannot change them. In addition:
- You cannot create custom events.
- The agent strips exception messages from errors.
- The agent strips
QueryParametersfrom database segments.
Custom security settings
Advertencia
If you customize security settings, it may impact the security of your application.
If you need different security settings than default or high-security mode, you can customize these settings:
Setting | Effects on data security |
|---|---|
boolean | Default: To enable high-security mode, set this to |
boolean | Default: By default, you are sending some attributes to New Relic. If you do not want to send these default attributes to New Relic, set |
string | Default: (none) If there are specific attribute keys that you do not want to send to New Relic in transaction traces, identify them using For examples of how to disable the recording of each attribute, see their descriptions on the Go agent attributes page. |
boolean | Default: By default, the agent records events sent to the Event API using |