FusionReactor Observability & APM

Installation

Downloads

Quick Start for Java

Observability Agent

Ingesting Logs

System Requirements

Configure

On-Premise Quickstart

Cloud Quickstart

Application Naming

Tagging Metrics

Building Dashboards

Setting up Alerts

Troubleshoot

Performance Issues

Stability / Crashes

Debugging

Blog / Info

Customers

Video Reviews

Reviews

Success Stories

About Us

Company

Careers

Contact

Contact support

Coming Soon | FusionReactor Product Update | Q2 2026

Product Update

Your Instrumentation, Your Backend: The FusionReactor Agent Is Getting a Lot More Flexible

FusionReactor has always offered something no other observability tool can match: deep, out-of-the-box instrumentation for ColdFusion applications. The kind of insight — CFML request transactions, query performance, error context — that you simply cannot get by wiring up a generic OTel agent.

The trade-off, until now, has been that to get your metrics, logs, and traces (MLT) out of the FusionReactor agent and into a storage and analytics backend, you needed an OpsPilot subscription.

That’s about to change.

Ship Your FR Data to Any OTel Backend — No OpsPilot Plan Required

Coming next quarter, the FusionReactor Agent will be able to ship your MLT data directly to any OpenTelemetry-compatible provider. Datadog. Grafana Cloud. New Relic. Honeycomb, Splunk, Dash0, etc. Your own self-hosted OTel collector. Wherever your telemetry stack already lives.

No OpsPilot subscription needed to get your data out.

For the first time, you can use FusionReactor’s unmatched ColdFusion instrumentation and send that data wherever you want — on your terms, in your existing stack.

For teams already invested in a preferred observability backend, this removes the biggest barrier to adopting FusionReactor. You get the depth of FR’s ColdFusion-specific instrumentation — the part no one else does — without paying for a second observability platform to store it.

What this unlocks:

  • Ship ColdFusion MLT data directly into Datadog, Grafana, New Relic, or any other OTel-compatible backend
  • No requirement for an OpsPilot license just to extract and route your telemetry
  • Use FusionReactor’s instrumentation as a best-in-class ColdFusion data source, feeding into your existing observability workflows
  • Switch or consolidate backends in the future without re-instrumenting your applications

This is particularly significant for ColdFusion teams. Java applications have had flexible OTel instrumentation options for some time. CF has not — until now, FR’s deep CF insight has been tied to the OpsPilot pipeline. This update breaks that dependency.

Still Want the Full Experience? That’s What OpsPilot Is For

Routing your data to an external backend is the right choice for some teams. But for teams who want more than storage — who want AI-powered analysis, anomaly detection, natural language querying, and a purpose-built observability experience — OpsPilot remains the most powerful option.

OpsPilot gives you:

  • AI-powered anomaly detection that identifies issues before they impact users
  • Natural language querying — ask questions about your system in plain English
  • Automated root cause analysis to cut troubleshooting time dramatically
  • OpsPilot Hub — a central knowledge base combining your organisation’s context with your telemetry data
  • Integrations with Jira, Slack, and Microsoft Teams for streamlined incident response
  • Pre-built dashboards for logs, traces, metrics, and ColdFusion-specific performance data
  • Predictive analytics to help prevent future incidents

OpsPilot isn’t just a place to store your data. It’s an AI companion that understands the relationships between your metrics, logs, traces, and application behaviour — and helps your whole team act on them, not just your engineers.

The choice is simple: bring your own backend and use FR’s instrumentation as a data source, or use OpsPilot and get the full AI-powered observability experience on top.

One More Thing: No More Email Auth Headaches

Alongside the OTel routing update, the FusionReactor Agent will also ship with its own built-in email service.

If you’ve ever had an alert fail because of an SMTP configuration issue, expired credentials, or a blocked relay — you’ll know exactly why this matters. The agent will handle email delivery natively, meaning:

  • Alerts and notifications send reliably, without depending on your own email infrastructure
  • No SMTP configuration required during setup, but you can use your own SMTP if you prefer
  • No credential expiry silently breaking your notification pipeline
  • Faster time-to-value for new users — alerting works from day one

It’s a quieter feature than OTel routing flexibility, but its impact on daily operations is real. Reliable alerting is non-negotiable for effective observability, and removing this source of friction makes FusionReactor significantly easier to run in production.

Two Paths. One Agent. The Best ColdFusion Instrumentation Available.

These updates reflect where FusionReactor is heading: an agent that fits into your stack, rather than one that demands you reorganise your stack around it.

Whether you route your data to an existing OTel backend or choose the full OpsPilot experience, you’re getting the same thing at the foundation — the deepest, most reliable ColdFusion and Java instrumentation available. What you build on top of that is now up to you.

Both features are coming next quarter. In the meantime, FusionReactor is available now — try it free and see what your applications look like with full visibility.