EOL NOTICE
From April 2022, we don't support the C SDK capability. For more details, see our Support Forum post.
Due of the nature of the C SDK, you have direct control over what data is reported to New Relic. To ensure data privacy and to limit the types of information New Relic receives, no customer data is captured except what you supply in your API calls. In addition, the C SDK reports all data to New Relic over HTTPS.
For more information about our security measures, see our security and privacy documentation, or visit the New Relic security website.
Default security settings
By default, this is how the C SDK handles the following potentially sensitive data. For more information, including code values and examples, see the C SDK documentation about data structures on GitHub.
Type of information | C SDK data security |
---|---|
Datastore instance name or database name | The
|
SQL | The |
The audit log is a plain text logging of all data sent to New Relic by the C SDK. When starting the C SDK daemon, add bash
TipTo see all of the available options for the C daemon: At the command line, type: bash
|
Customize security settings
If the default settings do not work for your business needs, you can customize how information is sent to New Relic by altering the newrelic_datastore_segment_config_t
and the newrelic_transaction_tracer_config_t
.
Caution
If you customize your configuration, it may impact the security of your application.