If you are not receiving traces and metrics in your AppOptics dashboard these are some options to troubleshoot.
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 disabled
Your application will run normally, but no metrics or traces will be collected.
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?.
The agent log messages are sent to stderr, which is usually written to the log file configured for the web server.
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.
When the APM Integrated Experience is enabled, AppOptics shares a common navigation and enhanced feature set with the other integrated experiences' products. How you navigate the product and access its features may vary from these instructions. For more information, go to the APM Integrated Experience documentation.
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.