Migrate the Python Library from AppOptics to SolarWinds Observability
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
xx-yyis determined by the URL you use to access SolarWinds Observability, see 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.
AppOptics users can use the following information to migrate to SolarWinds Observability.
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.
Uninstall the AppOptics agent.
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
importstatement to add the
appoptics_apmmodule to the application code, remove the added statement from your code.
appoptics-apmpackage and remove it from your application dependencies.
Install the SolarWinds Observability Python Library. See Install the Python Library.
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 instrumention SDK have a corresponding OTel API available for use. The current gaps listed below will be addressed in upcoming releases:
- Custom Metrics
- Custom Transaction Name