Architecture

The MyDecisive SmartHub (MyDecisive SmartHub) integrates with the telemetry pipelines and storage solutions you’ve set up with a cloud service provider (CSP). The MyDecisive SmartHub is installed in its own Kubernetes (K8s) namespace, alongside your existing infrastructure.

This flowchart shows a generalized system that begins with telemetry data generated by application and infrastructure services and ends with specific types of storage that can be added and removed as needed.

Your infrastructure uses an OpenTelemetry (OTel) collector in your namespace to export telemetry data to both storage destinations and to the MyDecisive SmartHub in the MyDecisive namespace. The MyDecisive SmartHub then processes the data and automatically updates the OTel collector with optimized values.

Let’s dive into each of the namespaces in the diagram.

Infrastructure in Your Namespace

Your services generate logs, metrics, and trace data that is collected by a set of services called the OTel collector. The collector consists of one or more pipelines that consume, transform, and transmit telemetry data.

In general, OTel collector pipelines consist of:

• Receivers that gathers the data directly from data sources or through intermediary services.

• Processors that act on the data, such as by transforming, redacting, and sampling it.

• Exporters that transmit data to its next destination, such as backend storage.

Infrastructure in the MyDecisive Namespace

The MyDecisive SmartHub receives an identical copy of the data that the OTel Collector does.

The MyDecisive SmartHub consists of:

• An observer that processes telemetry data from a forked data pipeline in the OTel Collector and generates metrics.

• A metrics store that receives the telemetry data from the observer. The metrics store is implemented using Prometheus.

• A metrics evaluator that triggers events whenever certain conditions are met.

• An event handler to process those events.

• A variable store that stores environment variables and posts updates to the OTel processor. The variable store is implemented using Valkey.

Pluggable Storage Services

You can export data to different types of storage within or outside of your CSP. Depending on your organization’s requirements, these are typical storage solutions:

• Vendor - for external storage and other vendor services.

• Compliance - to satisfy regulatory requirements.

• Auditing - for review and assessment of data.

• Analytics - to create visualization and surface insights.