Export logs
Turn on log export in Settings > Account Settings, filter the Logs Dashboard and click Export. Each file holds up to 100,000 entries or 50 MB, so split large histories by app and date.
BMC Helix is retiring Stackify Retrace. After that date you can't log in, send data or open stored data. Here is what stops, what to export first, and a plan that keeps every app monitored while you switch.
From BMC Helix’s Stackify Retrace end-of-life letter and its follow-up guides.
| Topic | What BMC says |
|---|---|
| End-of-life date | March 31, 2027, for Stackify Retrace and for Premium support of Stackify Prefix. |
| Until then | Maintenance mode: no new features, only fixes for high-impact issues and security updates. |
| After the date | Retrace is SaaS-only, so there is no login, no data ingestion and no access to stored data. |
| Your data | Exporting is your job. Logs export as files of up to 100,000 entries or 50 MB each, and custom dashboards as PDF reports. |
| Migration | No automated conversion to OpenTelemetry or any other tool. Every option means replacing the Retrace agents and profilers. |
| Support | Stackify support stays available at support@stackify.com until March 31, 2027. There is no extended support after that. |
Retrace has no self-hosted version to fall back on. When the service switches off, the agents on your servers have nowhere to send data, your dashboards and alerts stop, and the history stored in Retrace can no longer be opened.
Until then Retrace keeps running, but BMC calls it functionally stabilized: no new features, only critical fixes. Don't count on support for new runtime or framework versions. If you upgrade one before you move, check that Retrace still covers it.
BMC also points to a technical reason: Retrace relies on underlying cloud services that reach their own end of life in March 2027.
Stackify Prefix, the free code profiler developers run on their own machines, is not being shut down. BMC says customers are expected to be able to keep using it after March 31, 2027. What ends is Premium support: Prefix gets no further updates and no support guarantees. BMC also says Prefix’s premium features are now available at no cost.
Without updates, Prefix may not keep up with new runtime versions. It still helps with local debugging, but it does not replace production monitoring, which is what Retrace did.
Retrace data does not move to any other tool. The export guide walks through every step.
Turn on log export in Settings > Account Settings, filter the Logs Dashboard and click Export. Each file holds up to 100,000 entries or 50 MB, so split large histories by app and date.
Email each custom dashboard to yourself as a PDF report for the time ranges you need. Public dashboard links stop working when Retrace does.
Alert rules, monitor thresholds, notification routing and your app and server list have no documented export. Record them now so you can rebuild them.
BMC lists four paths. Each one means replacing the Retrace agents, either with OpenTelemetry or with another vendor’s own agents.
For organizations with enterprise operations needs or an existing BMC Helix footprint. BMC says it is not a like-for-like replacement for Retrace, and it needs a new Helix tenant and an enterprise license.
For teams that want a tool they don’t have to run. Trial a shortlist on real traffic. Some vendors accept OpenTelemetry, others use their own agents, and pricing models differ.
Jaeger or Grafana Tempo with Prometheus and Loki, or an OpenTelemetry-native backend. You run, scale, secure and build alerting for it yourself.
An OpenTelemetry Collector sends the same data to two tools at once, so you can compare them on real traffic. Expect some extra cost and noise while both run.
The order BMC itself recommends. Each app stays monitored by one of the two tools the whole time.
Each app, its language and runtime, where it runs, and which Retrace features your team actually uses.
Logs and dashboard PDFs for audits and incident reviews, plus a written copy of your alert rules.
Install it on a staging copy of one or two apps, or on a server you take Retrace off, and compare its numbers with Retrace's for a few days.
Move apps in small groups, keeping Retrace on each one until the new tool covers it. Then uninstall the Retrace agents, well before March 31, 2027.
Atatus is a commercial APM platform with its own agents that also accepts OpenTelemetry, so it fits the second and fourth paths. You can run it on one app while Retrace keeps watching the rest. See the full comparison.
| What you use in Retrace | Where it is in Atatus |
|---|---|
| Application performance and transaction traces | APM with distributed tracing |
| The .NET profiler (IIS, .NET Framework, .NET Core) | .NET APM, with a no-code profiler mode for IIS, .NET Framework and .NET 5+ |
| Errors and exceptions | Error tracking inside APM, linked to the request that failed |
| Centralized logs | Log management, with logs linked to traces |
| Server metrics and monitors | Infrastructure monitoring |
| Alerts | Alerting |
| Custom dashboards | Dashboards |
| Real user monitoring | Real user monitoring |
| OpenTelemetry data | OpenTelemetry (OTLP) ingest |
Logs, dashboards and the settings you have to write down, before March 31, 2027.
Read the guideReplace the Retrace .NET profiler with the Atatus agent on IIS, .NET Framework and .NET 5+.
Read the guideWhat Retrace installed in each language, and how to swap it for the Atatus agent.
Read the guideWhat OpenTelemetry captures compared with Retrace, and how to send the same data to two tools while you choose.
Read the guideThe overall plan for moving every app, language and alert off Retrace.
Read the postHow the two compare on APM, logs, real user monitoring and setup.
Read the comparisonThe main tools Retrace teams are looking at, and who each one suits.
See the alternativesPrefix keeps running but stops getting updates. Local tools, most of them free, that do the same job.
Read the postStackify Retrace reaches end of life on March 31, 2027. BMC Helix says it is SaaS-only, so after that date customers can't log in, send data or open stored data. Until then it runs in maintenance mode, with fixes for high-impact issues and security updates only.
Not the tool itself. BMC Helix says customers are expected to be able to keep using Prefix after March 31, 2027, but Premium support ends and Prefix gets no further updates or support guarantees.
No. BMC Helix says there is no automated conversion from Retrace to OpenTelemetry or to any other platform. You replace the Retrace agents with the new tool’s instrumentation, and you export any history you need to keep yourself.
You can no longer open it. BMC Helix says customers are responsible for exporting data before the end-of-life date, and that remaining data is then handled in line with regulatory and compliance requirements.
It depends on how many apps and languages you run. Start with a pilot on one app, then move the rest in small waves, keeping Retrace on each app until the new tool covers it. Starting early leaves time to fix surprises before the deadline.
Yes. Atatus has its own agents and also accepts OpenTelemetry data over OTLP, so you can use either. With an OpenTelemetry Collector you can also send the same data to Atatus and another tool while you compare them.
Install Atatus on one app today and run it next to Retrace. By March 2027 you will already know what normal looks like in the new tool.