Migrate from AppOptics libraries to SolarWinds Observability libraries

SolarWinds Observability SaaS and its APM libraries are constantly being improved with new features and enhancements. In contrast, AppOptics and its agents are not under active development.

Reasons to upgrade

Upgrade to the SolarWinds Observability libraries to take advantage of the following:

• Cutting-edge development and codebase: The SolarWinds Observability APM libraries leverage the latest codebase and are undergoing active development. This ensures that you're equipped with the most advanced features and capabilities, keeping your monitoring solutions up-to-date and future-proof.

• Updated language runtime support:SolarWinds Observability APM libraries support newer language runtimes and their corresponding components and libraries. If your applications are built using modern technologies and the latest programming languages, use SolarWinds Observability libraries to effectively monitor your applications.

• End of updates for AppOptics: AppOptics APM agents are no longer receiving updates. By upgrading to SolarWinds Observability libraries, you ensure continued support and access to the latest features, fixes, and enhancements.

• OpenTelemetry adoption: The SolarWinds Observability Go, Java, Node.js, Python, and Ruby libraries are built with OTel packages and agents, with additional libraries in the process of moving to OTel. This ensures compatibility with evolving industry standards, a vendor-agnostic API for manual instrumentation, and support for standard exporters, all while retaining the distinctive benefits offered by SolarWinds.

• Expanded functionality: SolarWinds Observability libraries have expanded coverage of platforms and components compared to AppOptics agents, as we leverage features from OpenTelemetry and contribute to the community to improve observability tooling. This means more accurate insights, faster issue identification, and ultimately, a more reliable and efficient application environment.

• Compatibility with SolarWinds Observability SaaS: SolarWinds Observability libraries are designed to work with SolarWinds Observability SaaS. Migrating to SolarWinds Observability SaaS libraries is a crucial part of your transition to SolarWinds Observability SaaS.

Considerations for upgrading

AppOptics APM libraries support some legacy language runtimes that the SolarWinds Observability libraries do not. If your application runs on older, unsupported runtimes and components, consider updating your applications so you can take advantage of the latest features and fixes in the SolarWinds Observability libraries. In the meantime, continue using the AppOptics agents.

Review the components supported by the legacy agents and those supported by the SolarWinds Observability libraries to determine whether to stick with the AppOptics agent or upgrade to the SolarWinds Observability library.

Language	AppOptics agent support	SolarWinds Observability library support
Node.js	Legacy agent: components supported	SolarWinds Observability library: components supported
Go	Manual instrumentation via proprietary API	SolarWinds Observability library: components supported
Java	Legacy agent: components supported	SolarWinds Observability library: components supported See also Supported libraries, frameworks, application servers, and JVMs in the OpenTelemetry Java Instrumentation documentation.
.NET	Legacy agent: components supported	SolarWinds Observability library: components supported
PHP	Legacy agent: components supported	SolarWinds Observability library: components supported
Python	Legacy agent: components supported	SolarWinds Observability library: components supported
Ruby	Legacy agent: components supported	SolarWinds Observability library: components supported

What do I need to keep in mind when upgrading to SolarWinds Observability libraries?

Before upgrading to the SolarWinds Observability libraries, consider the following:

• Ensure that your platform, language runtime and components, and application language are supported. If you are using unsupported legacy runtimes and components, continue using the AppOptics APM agents. Consider upgrading your application.

• Remove the AppOptics APM agent from your application before using the SolarWinds Observability library. Do not run other APM libraries alongside the SolarWinds Observability library.

• Review your application's API calls for the old AppOptics agents. After upgrading, replace the AppOptics calls with calls to the SolarWinds Observability API.

• Review your custom configurations. After upgrading, manually migrate the settings to SolarWinds Observability library configurations as needed.

How to upgrade to SolarWinds Observability SaaS libraries

Find the instructions for your language's library below to upgrade to the SolarWinds Observability APM library. This upgrade involves uninstalling the AppOptics agent, installing the SolarWinds Observability APM library, and migrating your configurations and customizations to SolarWinds Observability SaaS.

Do not run other APM libraries alongside the SolarWinds Observability libraries. Remove other APM libraries from your application before using the SolarWinds Observability library.