Migrate the Python Library from AppOptics 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 apm.collector.xx-yy.cloud.solarwinds.com (where xx-yy is determined by the URL you use to access SolarWinds Observability SaaS, described in Data centers and endpoint URIs) using port 443. 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.

Migrate from AppOptics

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

1. Remove any references to the AppOptics custom instrumentation API in your application code.

   Save a list detailing your application's usage so that it can be updated for the SolarWinds Observability Python Library's API.

2. Uninstall the AppOptics agent.

   1. Undo the steps taken to load the agent into your application. See Enabling the Agent instructions in the AppOptics Administrator Guide.

      For example, if you used an import statement to add the appoptics_apm module to the application code, remove the added statement from your code.

   2. Uninstall the appoptics-apm package and remove it from your application dependencies.

3. Install the SolarWinds Observability Python Library. See Install the Python Library.

4. Update the instrumentation API, if needed. See SDK for more information.

   The SolarWinds Observability Python Library is an OpenTelemetry custom distro and supports the standard OTel tracing API.

   Most of the AppOptics instrumentation SDK have a corresponding OTel API available for use. Custom Metrics are not currently supported, but they will be added in an upcoming release.