Documentation forSolarWinds Observability SaaS

Migrate the Java Library from AppOptics to SolarWinds Observability

AppOptics users can use the following information to migrate to SolarWinds Observability SaaS.

Before you start

Verify the following to ensure the library can collect and transmit data:

  • The platform where your APM library will be installed is supported.

  • Your application components are supported by the library.

  • Your firewall configuration permits TCP/HTTPS/TLS outbound connections to otel.collector.xx-yy.cloud.solarwinds.com (or apm.collector.xx-yy.cloud.solarwinds.com when using legacy mode) port 443, where xx-yy is determined by the URL you use to access SolarWinds Observability SaaS, described in Data centers and endpoint URIs. See Firewall or access control requirements.

    If your firewall or access control requirements do not allow such connections, configure the library to send data through a proxy.

Remove other APM libraries from your Java application before using the SolarWinds Observability Java Library.

Uninstall the agent for AppOptics

Follow the instructions in the Uninstall the Java Agent topic in AppOptics documentation to disable, 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.

Install the library for SolarWinds Observability

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

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.