Telecom Connectors

TM Forum aligned northbound integration. Plug DriftMind into your existing PM, assurance, and FM stack without rewriting your OSS. Read live KPIs, publish predictive alarms and service-impacting events through standard interfaces.

Native Integration

The most direct way in. Use DriftMind's own REST API, stream KPIs through Kafka, or integrate with the official Python client. The same code works against SaaS, Edge, and Enterprise deployments.

DriftMind REST API

Push KPI observations, fetch predictions, and manage forecasters, patterns, and attachments directly. OpenAPI 3.0 documented; same endpoints power SaaS, Edge, and Enterprise.

/api/driftmind/v1 · OpenAPI 3.0 · token auth

Native Kafka Ingestion

Subscribe DriftMind directly to your Kafka topics. Configurable consumer groups, partition strategy, and offset handling. Backpressure-aware for high-throughput KPI streams from millions of cells.

Kafka consumer · per-forecaster topic mapping

Python Client

Official Python library wrapping the REST API. Capability-aware — automatically detects whether Echo is available on the target deployment. Same code works against SaaS, Edge, or on-device.

driftmind-client · SaaS + Edge + Enterprise

Inbound OSS Protocols

Read live KPIs and event streams from the platforms you already run — modern routers, legacy SNMP-based equipment, mediation Kafka topics, and OSS REST APIs.

SNMP

Read PM counters and trap streams from network elements that still speak SNMP — which, in practice, is most of them. v2c and v3 supported.

PM counters · trap ingestion · v2c / v3

gNMI

Streaming telemetry for modern routers and switches. Subscribe to YANG-modelled paths and ingest at line rate.

Streaming telemetry · YANG · gRPC

NETCONF

YANG-modelled configuration and state retrieval. Read counters and operational state without depending on vendor-specific MIBs.

YANG models · operational state

Kafka

Subscribe to PM, event, and telemetry topics published by mediation layers. Consumer-group aware, with backpressure-friendly batching.

PM streams · event topics · mediation output

REST / OpenAPI

For modern OSS platforms with documented APIs. Includes JDBC and CSV fallbacks for legacy systems where REST isn't available.

Modern OSS APIs · JDBC · CSV

MQTT

Useful for IoT-flavoured KPI sources, smart-grid edge, and modern probe deployments that bypass legacy mediation.

Probe telemetry · IoT KPI streams

Alerting & Fault Management

What happens when DriftMind detects an anomaly or matches an Echo pattern. Publish to your FM stack via TM Forum standards, or route to the channels NOC and SOC operators already watch.

TMF642 Alarms

Publish DriftMind anomalies as standards-compliant alarms into your FM stack. Severity, perceived severity, ack and clear lifecycle states follow the spec.

TM Forum Open API · alarm lifecycle

TMF656 Service Problems

Publish service-impacting events for end-to-end correlation. Lifecycle states, related entities, and originating alarms map cleanly to the customer's catalogue.

TM Forum Open API · service problem events

Webhooks

Generic HTTP POST to any URL. Severity routing, retry with exponential backoff, HMAC signing for downstream verification. Useful for custom mediation layers and bespoke integrations.

HTTP POST · HMAC signed · retry policy

Slack & Microsoft Teams

Channel-based notifications with severity routing. Custom templates per channel. Interactive ack / snooze actions. Useful for engineering bridges and incident war rooms.

Slack apps · Teams incoming webhooks

PagerDuty & Opsgenie

Incident routing for on-call rotations. DriftMind severity maps to incident urgency. Auto-resolve when the anomaly clears, no operator click required.

incident routing · auto-resolve · escalation

ServiceNow ITSM

Create incidents in ServiceNow when DriftMind events need ticketed workflow. Auto-populate impacted service, location, and originating telemetry from the CMDB.

ServiceNow REST · CMDB lookup · ITSM

Compatible OSS Platforms

DriftMind sits alongside the assurance and FM platforms you already run. Outputs flow back via TMF642 / TMF656 — no custom adapter project required.

PM & Service Assurance

• ProOptima
  REST · Kafka · SNMP
  Performance management & assurance
• InfoVista
  REST · SNMP · NETCONF
  Service assurance & testing
• TEOCO
  REST · Kafka · SNMP
  Cost & service management
• Amdocs
  REST · TM Forum APIs
  BSS / OSS suite
• Nokia AVA
  REST · Kafka
  Network & service intelligence

Fault Management & Event Correlation

• NetExpert
  TMF642 · SNMP · REST
  FM & event correlation
• Netcool / OMNIbus
  TMF642 · SNMP · syslog
  IBM · event consolidation
• ServiceNow
  REST · TM Forum APIs
  ITSM & ITOM workflows
• Operations Bridge
  REST · SNMP
  OpenText (ex-Micro Focus)

Why It Matters

Standards-Aligned

TMF642 and TMF656 are the industry standards for alarm and service problem exchange. Speaking them fluently means DriftMind drops into existing FM stacks with minimal integration risk.

Bidirectional

Read PM and event streams from your existing assurance stack. Write predictive alarms and service problems back through standard northbound interfaces. Operators stay in their FM tool — they just see better alarms.

Deploys in Under 2 Weeks

No data lake migration. No PM platform rip-and-replace. Connect via REST or Kafka, map your KPIs, start receiving anomaly forecasts and pattern matches inside one sprint.