Integrations
Integrations allow Operyn to both ingest telemetry from your infrastructure and dispatch alerts to the platforms your team already uses. Operyn distinguishes between Ingestion Sources (inbound data) and Notification Channels (outbound alerts).
Ingestion Sources
Ingestion Sources are the external systems that provide the raw logs, metrics, and deployment events that Operyn analyzes. These are managed via the Integrations section in the Dashboard.
| Source | Status | Description |
|---|---|---|
| AWS CloudWatch | ✅ Ready | Automated CloudFormation stack to forward logs and metrics. |
| GCP Cloud Logging | 🛠️ Beta | Zero-touch ingestion for Google Cloud Platform. |
| Prometheus | ✅ Ready | Pull metrics directly from Prometheus exporters or Pushgateway. |
| Custom / API | ✅ Ready | Use our Ingestion API to send data from any source. |
Notification Channels
Notification Channels allow Operyn to correlate and dispatch alerts when an incident is detected and diagnosed.
| Channel | Type | Primary Use Case |
|---|---|---|
| Slack | Generic/Env | Posts messages to channels via incoming webhooks. |
| Discord | Multi-tenant | Sends rich embeds with severity, description, and dashboard links. |
| Env-only | Dispatches SMTP alerts to one or more recipients. | |
| Jira | Multi-tenant (Encrypted) | Creates tickets for HIGH and CRITICAL incidents. |
| Webhook | Multi-tenant | POSTs a full JSON payload to any HTTP endpoint. |
Configuration
All integrations are configured via the Console → Integrations page (/console/integrations). The older /console/settings/integrations path redirects to the new location for compatibility.
Ingestion Sources
Connect AWS CloudWatch or GCP Cloud Logging to forward logs and metrics into Operyn for analysis. See the individual integration guides for detailed setup instructions.
Notification Channels
Configure where incident alerts should be delivered:
| Channel | Setup | Use Case |
|---|---|---|
| Slack | Incoming webhook | Real-time incident awareness in team channels |
| Discord | Server webhook | Rich embeds with severity and Dashboard links |
| Jira | Encrypted credentials | Ticket creation for HIGH/CRITICAL incidents |
| PagerDuty | Events API v2 | Route high-urgency incidents to on-call rotations |
| Datadog | Events API | Push incidents into Datadog Event Explorer |
| Grafana | Annotations API | Write incident markers into Grafana dashboards |
| Webhook | Custom endpoint | Custom integrations, paging systems, internal tools |
| Coming soon | SMTP alerts to distribution lists |
All notification channel credentials are encrypted at rest in the platform vault. Configuration is workspace-scoped (Org Config), allowing granular per-team alerting without infrastructure changes.
See the Notification Channels Setup Guide for detailed step-by-step instructions.
API Flow
When the incidents module in core-platform processes an event:
- Diagnosis: AI analyzes the incident.
- Dispatch:
ProcessEventUseCasecalls the registered integration services. - Notification: the notifications module in
core-platformexecutes dispatch (Slack/Discord/Email/Webhook/PagerDuty/Datadog/Grafana). - Jira: the incidents module in
core-platformcreates/updates Jira tickets and adds comments using the stored (encrypted) Jira integration config.
Troubleshooting
- Test Connections: Use the "Test" button in the Dashboard for each integration to verify connectivity instantly through
core-platform. - Service Logs: Check
docker logs core-platformfor backend integration and dispatch errors. - Payload Inspection: Use a tool like Webhook.site as a destination for the Generic Webhook integration to see exactly what Operyn is sending.
Console Experience
The Integrations page is designed as a first-class operations surface rather than a nested settings form. Use it when you need to:
- Connect or review ingestion sources.
- Verify organization-level notification wiring.
- Run smoke tests before enabling alerts for a team.
- Keep integration setup distinct from profile, billing, and team administration tasks.
Best Practices
- Tiered Alerting: Use Discord/Slack for real-time noise and Jira only for actionable HIGH/CRITICAL incidents.
- Secure Webhooks: Always use
httpsfor generic webhook endpoints. - Dedicated Recipient: For email alerts, use a distribution list or a shared inbox (e.g.,
ops-alerts@company.com).