MyDecisive Open Sources the Smart Telemetry Hub

We're thrilled to announce that we released our production-ready implementation of OpenTelemetry and are contributing the entirety of the MyDecisive Smart Telemetry Hub, making it available as open source.

The Smart Hub is designed to run in your existing environment, writing its own OpenTelemetry and Kubernetes configurations, and even controlling your load balancers and mesh topology. Unlike other technologies, MyDecisive proactively answers critical operational questions on its own through telemetry-aware automations and the intelligence operates close to your core infrastructure, drastically reducing the cost of ownership.

We are contributing Datadog Logs ingest to the OTel Contrib Collector so the community can run all Datadog signals through an OTel collector. By enabling Datadog's agents to transmit all data through an open and observable OTel layer, we enable complete visibility across ALL Datadog telemetry types.

Why Open Source the Technology Now?

We believe that to drive mass adoption and build the community required for this next generation of operational control, the technology must be free and open. We are contributing to the CNCF to rise above the market noise of closed, unproven "AI-based incident response" tools. The Smart Hub's open-source nature proves our commitment to community-led innovation.

This move drastically reduces the cost of ownership and fundamentally transforms the value you get for your observability investment.

Why Should I Choose the Smart Telemetry Hub?

The Smart Hub is not just another observability solution that you run on your own. While it is built as a cloud-native solution on Kubernetes and utilizes OpenTelemetry to process and work with your pre-existing observability set up.

For years, customers have challenged us: "Can you truly help us reduce MTTR (Mean Time To Resolution)?" Our answer, finally realized with the Smart Hub, is a resounding "Yes."

The Hub is designed to autonomously control and manage production infrastructure changes. It doesn't just look at data; it acts on it. The Hub answers the critical operational questions on its own:

• Should we execute a roll forward or initiate a rollback?

• Which services are unhealthy, and how did they get that way?

• If a production component is alerting, what would be the best action? Restart? Fail over? Scale up or down?

As the technical teams behind web giants (Walmart.com, Amazon.com) to open big data platforms (Hortonworks, Citus Data, Imply) to observability (New Relic) we have been in the trenches fire fighting and taking control of data too. We continue to do that and are contributing our platform to make OpenTelemetry easier for everyone. When we see an issue affecting us we fix it. The need for interoperability has long been discussed and past efforts have failed. We thought a neutral ingest as we introduced into our customers recently was a good place to start. Watch for what is next!

Aside from being both production-hardened and open source, MyDecisive has many additions to and super charged features beyond OpenTelemetry. Like other offerings we also save you 70-90% on your cloud billing.

What We're Contributing

We are contributing Datadog Logs ingest to the OTel Contrib Collector and it's available in v0.140.1. Currently Datadog formatting ties you to Datadog's preprocessing path (DD Agent and Vector for transformation/pre-processing). We are introducing a vendor-neutral ingest. Adding logs to OTel breaks that dependency and reduces switching cost through use cases like data filtration.

• OTel Collector Datadog Receiver: add Logs support. Today the receiver reliably handles traces + metrics from Datadog APM/agents. We're contributing logs ingest so OTel can accept all three signals (metrics, logs, traces) from Datadog's OpenSource agent.

We in effect turn OTel into a neutral "man-in-the-middle" that can receive → transform → export Datadog-originated telemetry using open processors/exporters. The benefit is that OpenTelemetry running inside the SmartHub delivers pipeline observation + closed-loop automations to cut cost, boost reliability, and eliminate lock-in with a single, centralized control plane.

What this unlocks for Users and the OTel Community

By making transformations visible, debuggable, and standardized - MyDecisive turns OTel from a passive transport layer into an active, trustworthy, easy-to-adopt-and-scale telemetry fabric. This release is the difference between collecting data and understanding data - and it's foundational to enabling intelligent automation, accurate alerting, and the future of observability.

OpenTelemetry combined with MyDecisive's Observers, Automations, and Operational Insights, OTel gains those same powers openly - and with real-time feedback loops, normalization, filtering, and routing now occur seamlessly and transparently.

With this contribution users unlock:

• Full "M-L-T" coverage: One receiver path for Metrics, Logs, Traces from Datadog → OTel → any backend.

• Open, auditable transforms: Use OTel available components, specifically processors, for customized and fully-controlled / managed telemetry stream capabilities (attribute edits, redaction, sampling, routing). No more black boxes at the vendor ingest layer.

• Cost discipline upstream: Pre-ingest / Pre-processing controls (drop / aggregate / sample) reduce downstream volume and spend - with evidence in OTel pipelines.

• Vendor choice: Forward the same Datadog-originating data to Datadog and/or alternatives without re-instrumenting your agent fleet.

How to Get It

Join the MyDecisive community at Github or below. We look forward to seeing you!

• Download and Install the MyDecisive Smart Hub: Docs Link

• Checkout the e2e Lab for DD logs → OTel → anywhere: Labs Link

• Join our Community Slack: Link