You can install the New Relic C SDK on a Docker container (or other container) to monitor one or more of your C applications.
- Meet C SDK requirements
- C SDK version 1.2 or higher
Data transmitted from the agent to the daemon is not encrypted. We recommend only using a private network connection between the agent and daemon. This only applies when the agent and daemon are running on different hosts.
To install C SDK for a container environment, we recommend installing the C SDK daemon on a separate docker container:
If you are using Docker, you can use the C SDK daemon image on Dockerhub.
Start the daemon using
--addressargument is used to set a port where the daemon is accepting connections. The
--watchdog-foregroundargument ensures that the daemon runs in the foreground.
Then, use the C SDK in your containerized application:
- Follow the steps to add the C SDK to your code.
- Point the C SDK to the daemon by adding a
newrelic_initcall and passing a valid
addressargument. The value for this argument must be
HOSTis the name or IP address of the host where the daemon is running, and
PORTis the port number where the daemon is listening.
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.