Welcome to SmartHub
MyDecisive's SmartHub comes with a modular snap-in architecture. Octant uses it and so can you. Learn more through examples here in our platform pages.
MyDecisive SmartHub is a cloud-native control plane that runs inside your existing OpenTelemetry, Kubernetes, and Prometheus stack — turning telemetry into real-time action instead of another dashboard to watch.
Key capabilities
Three building blocks. One control gap closed. SmartHub reads telemetry and executes decisions on the wire — no manual triage, no decoding binary streams by hand.:
Adjust sampling, redact PII, and change log levels on live streams at the edge — no restarts, no config drift, results in milliseconds.
Turn tribal incident knowledge into one automation engine. Pre-built workflows fire the moment a condition is met.
Automation as Easy as IFTTT
Stop burying runbooks in a wiki. Put them in your infrastructure. Every SmartHub rule reads like code: a condition on your telemetry, an action on your infrastructure. Teams use it to cut real cost and drive MTTR toward zero.
| Trigger "IF This..." | Action "THEN That..." | Outcome |
|---|---|---|
| A customer-facing service's P95 latency exceeds 500ms for 3 consecutive minutes | Increase the deployment's HPA pod limit by 2, then notify the on-call engineer via Slack only if latency persists another 5 minutes | Fix performance issues before they escalate — and cut alert noise from transient spikes |
| A non-critical backend log line contains PII (e.g., an unredacted email address) | Redact the PII field in-stream, route the log to a low-cost S3 bucket for compliance retention, and withhold it from the SaaS vendor | Enforce data privacy automatically — and stop paying to ingest sensitive, non-actionable data |
| Trace sampling flags a request as low-value and originating from an internal staging IP. | Drop the sampling rate to 1% for 15 minutes and reroute the trace to a separate, non-indexed backend | Cut vendor ingestion costs during high-traffic internal testing, without losing visibility where it matters |
| 404 errors for a specific API endpoint drop to zero after a new deployment | Send a green-check to CI/CD, mark the runbook task complete, and silence 404 alerts on that service for 30 minutes | Confirm the fix worked and go quiet — no more chasing alerts you already resolved |
