Documentation forAppOptics
AppOptics will reach its End of Service Life on September 30, 2025. Migrate to the next generation APM solution before September 30. See FAQ, or contact appopticsng-questions@solarwinds.com for support. Documentation is no longer being updated, and some features or links may not work as described.

Upgrading the Java Agent

AppOptics agents are no longer 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.

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.

Upgrading to the SolarWinds Observability Java Library

The Java Instrumentation Library for SolarWinds Observability is compatible with the AppOptics collector. 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.

The Java Library for SolarWinds Observability is a custom distro based on the OpenTelemetry Java agent. The supported components, configuration, and instrumentation SDK are different from AppOptics.

Complete migration

SolarWinds recommends that you migrate completely from AppOptics to SolarWinds Observability. For more information about a complete migrations, see Migrate from AppOptics to SolarWinds Observability SaaS. To upgrade to the SolarWinds Observability Java Library as part of a complete migration, see Migrate the Java Library from AppOptics to SolarWinds Observability.

Partial migration

Alternatively, you can upgrade to the SolarWinds Observability Java Library but send data to AppOptics.

  1. Follow the instructions in Uninstall the legacy Java Agent to disable the agent, remove any SDK that is used, and uninstall the agent.

    For migration, you must remove references to the AppOptics SDK from your application. The AppOptics configuration file should not be reused for SolarWinds Observability.

  2. Follow the instructions in Add a Java service to set up your Java application as a monitored service in SolarWinds Observability.

  3. Before you restart the application, make the following additional configuration changes to have the SolarWinds Observability Java Library continue sending data to AppOptics:

    1. Set a valid AppOptics service key. See the SolarWinds Observability configuration options for the new configuration file and environment variable names.

    2. Set the collector configuration option to the AppOptics endpoint collector.appoptics.com:443. Use a config option, an environment variable, or a system property to override the default APM collector endpoint.

Upgrade to a newer version of the legacy AppOptics Agent

Java Agent

Linux

Upgrade the AppOptics Java agent by following the same steps as Installation.

We check if ./javaagent.json has been modified to retain any custom configurations you may have made. If the file has been modified, the new json file is stored under a different name, e.g. ./javaagent.json.6.18.0. As a next step you should transfer all your custom changes to ./javaagent.json.6.18.0, rename ./javaagent.json to something else such as ./javaagent.json.old and ./javaagent.json.6.18.0 to ./javaagent.json.

Windows

Download and run the latest AppOptics Java agent Windows installer from https://files.appoptics.com/java/latest/JavaAgent_Setup.exe.

Java SDK

AppOptics Java SDK is made available on Maven with group Id com.appoptics.agent.java and artifact Id appoptics-sdk. Simply set the version number to the the latest one according to our release notes. (SDK and Agent share the same version number.)

Our SDK jar can also be found within the installation folder of the AppOptics Java agent.