1. Home
  2. Guides
  3. Implementation
  4. Moving from Stackify Retrace to OpenTelemetry
IntermediateImplementation

Moving from Stackify Retrace to OpenTelemetry

BMC recommends OpenTelemetry as the standard to replace the Stackify Retrace agents. What OpenTelemetry captures compared with the Retrace profilers, how to send the same data to two tools while you choose, and how to send it to Atatus.

9 min readAtatus TeamUpdated November 16, 20267 sections

01Why OpenTelemetry, and why now

Instrument once, and the next change of tools is a config change.

Stackify Retrace shuts down on March 31, 2027. Its agents and profilers are proprietary and send data only to Retrace, so every Retrace customer has to replace them. BMC itself points customers to OpenTelemetry as the common standard for the replacement.

OpenTelemetry is an open source, vendor-neutral standard from the Cloud Native Computing Foundation for producing and sending traces, metrics and logs. It has SDKs for each language, automatic instrumentation for most of them, a standard protocol called OTLP, and an optional Collector that receives and forwards data.

It is not a tool you log in to. You still need a backend that stores the data and gives you dashboards and alerts. The benefit is that once your apps speak OpenTelemetry, changing backends means changing where the data goes, not reinstrumenting every app.

02What OpenTelemetry captures compared with Retrace

From BMC's own comparison of OpenTelemetry instrumentation with the Retrace profilers.

Comparable: incoming request tracing and route naming, outbound HTTP calls, distributed trace context across services, and unhandled exceptions with stack traces.

Partial: database call spans depend on the database client and version, and log integration varies in maturity by language. Validate both before you rely on them.

Different: web server and pipeline stage breakdowns, query parameters and row counts, caught (first-chance) exceptions, method-level call trees and continuous profiling are not captured by default. Add custom spans or manual recording where your team depends on them.

Check these against your own apps during a pilot. If your team leans on one of the gaps, plan the extra instrumentation, or use a vendor agent for that service.

03Zero-code or SDK: what each language offers

Most Retrace languages can start without code changes.

Zero-code instrumentation: OpenTelemetry offers it for Java, .NET, Python, JavaScript (Node.js), PHP and Go. It attaches at startup and instruments common frameworks and libraries for you.

Ruby: there is no Ruby zero-code agent. OpenTelemetry's eBPF instrumentation can capture Ruby HTTP and SQL calls on Linux at the protocol level, but for detail inside your app you add the OpenTelemetry SDK and instrumentation gems.

Signal maturity: traces are stable in all of these languages. Metrics and logs are stable for Java, .NET and PHP, and logs became stable in the JavaScript SDK 3.0 in October 2026. Logs are still in development for Python, and metrics and logs for Ruby. Check the OpenTelemetry language pages for the current status before you rely on them.

Atatus has OpenTelemetry setup pages for Java, Python, Node.js, Ruby, PHP and .NET. Start from the Atatus OpenTelemetry overview.

04Send OpenTelemetry data to Atatus

One endpoint and one header.

Endpoint: Atatus accepts OTLP traces, metrics and logs over HTTP at https://otel-rx.atatus.com.

Authentication: send your Atatus API key in the api-key header. Create a key with write permission in Atatus under Settings > Account Settings > API Keys.

From an SDK: set OTEL_EXPORTER_OTLP_ENDPOINT to https://otel-rx.atatus.com:443, OTEL_EXPORTER_OTLP_HEADERS to api-key= followed by your key, and OTEL_EXPORTER_OTLP_PROTOCOL to http/protobuf.

From a Collector: in your OpenTelemetry Collector, add an OTLP HTTP exporter that points at the same endpoint with the api-key header, and use it in your traces, metrics and logs pipelines. The Atatus Collector configuration page has the full YAML. Recent Collector releases rename the otlphttp exporter to otlp_http and keep otlphttp only as a deprecated alias, so switch to otlp_http when you upgrade.

See what you get once the data arrives on the Atatus OpenTelemetry page.

05Send the same data to two tools while you decide

BMC's "dual export" path, done with the Collector.

An OpenTelemetry Collector can send the same data to more than one backend. List two exporters in the same pipeline, one for each tool you are evaluating, and both receive identical traces, metrics and logs.

That lets you compare tools on the same real traffic without instrumenting twice. Expect some extra cost and noise while both run, and switch the second exporter off once you have chosen.

A Collector is optional for sending to Atatus, because SDKs can export straight to the endpoint. It earns its place when you want dual export, filtering, or masking sensitive data before it leaves your network.

06A migration plan that keeps every app monitored

Pilot, then waves, then remove Retrace.

Step 1: Export the Retrace logs and dashboards you must keep. See how to export Stackify Retrace data.

Step 2: Pick one service with steady traffic and a clear owner. Add OpenTelemetry instrumentation and use consistent service names, environments and versions from the start.

Step 3: Compare the new data with Retrace for a few days, and add custom spans for anything from the "different" list above that your team needs.

Step 4: Move the remaining services in small groups, removing the Retrace profiler from each one as it moves. Keep Retrace on a service until OpenTelemetry covers it.

Step 5: Remove the Retrace agents from your servers well before March 31, 2027.

07When an Atatus agent is the better fit

You can mix agents and OpenTelemetry in one account.

Some teams want the depth of a vendor agent for a few critical services. Atatus has agents for .NET, Java, PHP, Node.js, Python, Ruby and Go, and you can use them for some services and OpenTelemetry for others.

For .NET, the .NET migration guide covers the Atatus profiler mode, which needs no code changes. For the other languages, see replacing Stackify Retrace agents. To compare the two products feature by feature, see Atatus as a Stackify alternative.

FAQ

Frequently asked questions

Talk to an engineer
  • Yes. Atatus accepts OTLP traces, metrics and logs over HTTP at https://otel-rx.atatus.com, with your Atatus API key in the api-key header. You can send from an SDK directly or through a Collector.

  • Not by default. BMC's own comparison says request tracing, outbound calls and unhandled exceptions are comparable, but method-level call trees, caught exceptions, query parameters and pipeline stage breakdowns need custom instrumentation or a supplemental tool.

  • No. SDKs can send data straight to Atatus. A Collector is useful when you want to send the same data to two tools, filter it, or mask sensitive fields before it leaves your network.

  • Yes. Put two exporters in the same Collector pipeline, one for Atatus and one for the other tool, and both receive the same traces, metrics and logs.

  • Traces are stable in Ruby, but metrics and logs are still in development, and there is no Ruby zero-code agent, so you add the SDK. If you need Ruby metrics and logs today, check the current status or use the Atatus Ruby agent for those services.

Get started today

Monitor your applications with Atatus

Put the concepts from this guide into practice. Set up full-stack observability in minutes with no credit card required.

  • No credit card required
  • 14-day free trial
  • Setup in minutes
Keep reading
ImplementationBeginner

How to Export Your Stackify Retrace Data Before March 31, 2027

Stackify Retrace shuts down on March 31, 2027, and its data does not move to any other tool. Here is what you can export, the limits, what you have to write down by hand, and how to keep your history going in your next tool.

6 min
Read guide
ImplementationIntermediate

Migrating .NET Apps from Stackify Retrace to Atatus

Replace the Stackify Retrace .NET profiler with the Atatus .NET agent on IIS, .NET Framework and .NET 5+, one app at a time, so every app stays monitored until Retrace shuts down on March 31, 2027.

10 min
Read guide
ImplementationIntermediate

Replacing Stackify Retrace Agents: Java, PHP, Node.js, Python and Ruby

Swap the Stackify Retrace agent for the Atatus agent in Java, PHP, Node.js, Python and Ruby apps, one app at a time, so nothing goes unmonitored before Retrace shuts down on March 31, 2027.

9 min
Read guide