Integrations
Raincurve reads from the systems you already run and writes results back into the tools your teams use. This page lists supported source types by domain.
Data sources
| Domain | Source types | Used for |
|---|---|---|
| Network | SNMP traps and polling, syslog, streaming telemetry, flow records, neighbor discovery, routing state | Topology, alarms, causal grouping |
| Facilities | DCIM, power and environmental monitoring | Physical dependencies, tenant impact |
| Compute | Host metrics, out-of-band management, hardware health | Node health, placement |
| GPU and AI | GPU health and error counters, interconnect state, serving metrics | Inference and training reliability |
| Orchestration | Container orchestrators and batch schedulers | Workload placement, scheduling events |
| Cloud | Provider APIs for managed services, networking and load balancing | Cloud dependencies |
| Application | OpenTelemetry, logs, APM | Service symptoms and dependencies |
| Inventory | CMDB, IPAM, network source of truth | Entities, ownership, requirements |
| Change | Change management, CI/CD pipelines, maintenance calendars | In-flight work for verification |
Outputs
| Destination | What Raincurve sends |
|---|---|
| IT service management | One ticket per incident with origin, hypotheses, evidence and affected services |
| Chat | Incident summaries, verification results and approval requests |
| Paging | Routing to the team that owns the origin, not only the symptom |
| Change management | Verification results attached to proposed changes |
| Reporting | Post-incident timelines and audit records |
Normalization
Signals from different vendors and tools are normalized before reasoning: each entity is assigned a role (for example core, aggregation, access, server, GPU node, service), timestamps are aligned, and alarm types are mapped to a shared vocabulary. This is what lets the same model work across mixed-vendor estates.
Clock alignment
Management systems often disagree on time. Causal grouping tolerates moderate skew — in published testing, offsets up to 60 seconds had little effect — and known offsets between systems can be corrected at ingest.
ConnectorsSpecific connectors and versions for your environment are confirmed during the Tier 1 assessment. If a source is not listed, ask — most systems expose one of the formats above.