Troubleshooting (legacy agent)
The following content pertains to
AppOptics agents are no long receiving updates. The new SolarWinds Observability libraries are regularly updated with new features and improvements. If you are still relying on the AppOptics agents and your components are supported by the new libraries, consider migrating to SolarWinds Observability.
If you have already transitioned to the new SolarWinds Observability Nodejs Library, see the SolarWinds Nodejs Library documentation for troubleshooting information.
SolarWinds Observability libraries are not compatible with AppOptics agents. Do not use a mix of SolarWinds Observability libraries and AppOptics agents to instrument applications that are part of a distributed trace.
If you are not receiving traces and metrics in your AppOptics dashboard these are some options to troubleshoot.
Tracing disabled
The C++ addon requires gcc 4.7 and above, which means by default, it will not compile on older distros such as Ubuntu 12.04 or RHEL/CentOS 6. If the C++ addon fails to compile, the agent will output the following message during install, and go into no-op mode:
AppOptics bindings - failed to build, tracing disabledYour application will run normally, but no metrics or traces will be collected.
Nothing showing up in my.appoptics.com
The most likely cause is that your service key is not correct. There should be a message in the log saying
Server responded: Invalid API key
You can find the API Token for your Organization at https://my.appoptics.com/organization/tokens.
Another common cause is connectivity problems between the agent and the AppOptics server. If your server is behind a firewall, please see the FAQ: My application is behind a firewall. What IP address(es) do I need to whitelist?.
Where are the agent logs?
The agent log messages are sent to stderr, which is usually written to the log file configured for the web server.
More verbose logs
The log verbosity of the C++ addon and the agent log level can both be changed, see the Addon Log Level and Agent Log Level configuration options.
Do you have another APM agent installed?
It is not recommended to run other APM agents alongside our Node.js agent, as they can interfere and cause problems. Disable other APM agents from your application before starting your application with our agent.
The scripts are not supported under any SolarWinds support program or service. The scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.