Integrations
VerOps is built to sit alongside the tools you already run. It takes data in over open standards, sends alerts to the paging and chat tools your team uses, and gives data back through an API and exports.
- Telemetry in
- OpenTelemetry (OTLP)
- Notifications
- Nine channel types
- Delivery
- CI gates and GitHub checks
- Data out
- Public API, CSV, JSON
What connects to what
| Category | Integrations | Used for |
|---|---|---|
| Telemetry | OpenTelemetry SDKs and Collector, VerOps Java agent, Kubernetes (Helm) | Traces, metrics and logs |
| Cloud | AWS CloudWatch, Azure Monitor | Cloud resource metrics |
| Chat | Slack, Microsoft Teams, Discord | Alert notifications |
| Paging | PagerDuty, Opsgenie | Alert notifications and workbook actions |
| Ticketing | Jira | Issues from alerts and workbooks |
| Generic | Email, SMS, webhooks, HTTP actions | Anything else |
| Delivery | CI pipelines (trigger and poll API), GitHub check runs | Release gates |
| Directory | Microsoft Entra ID, CSV | User details for IT asset management |
| AI models | Anthropic, OpenAI, Azure OpenAI, Mistral, OpenRouter, Ollama, OpenAI-compatible | Vera, Sentinel and AI workbook nodes |
| AI agents | HTTP events, Model Context Protocol (MCP) | Sending runs to Sentinel |
| API | Public API at api.verops.io | Custom metrics and events in; platform data out |
How VerOps fits with your existing tools
You do not have to replace everything at once.
Keep your instrumentation
Services already instrumented with OpenTelemetry can send to VerOps by changing the exporter endpoint and adding a key. A Collector can send to more than one backend while you compare.
DocumentationKeep your paging tool
If your on-call already lives in PagerDuty or Opsgenie, route VerOps alerts there instead of using VerOps schedules.
DocumentationKeep your ticketing
Alerts and workbooks can open Jira issues, so follow-up work stays where it is tracked today.
DocumentationKeep your asset records
Import existing asset lists from CSV or the API, and let agents attach to those records.
DocumentationTake your data with you
Read data over the public API, export tables and reports as CSV or PDF, and export dashboards as JSON.
DocumentationGate releases in your own pipeline
Any CI system that can make an HTTP call can trigger a workbook and wait for its pass or fail result.
Documentation
Public API
- 01
Create an API-scoped key
Send it in the X-Api-Key header or as a Bearer token.
Documentation - 02
Send custom data
Push your own business metrics and events.
POST https://api.verops.io/v1/custom/metrics POST https://api.verops.io/v1/custom/events - 03
Read it back
Query custom data, or read the metrics, logs, alerts and inventory VerOps already holds.
Documentation
Read more in the docs
Try it on your own systems
Create a workspace, or tell us about your environment and we will walk you through it.