IntegrationsNotifications
Notifications
Configure alerts via Slack, Teams, Jira, PagerDuty, or webhooks.
Notifications
Valqore pushes alerts on BLOCK verdicts, critical findings, configuration drift, triage incidents, and score drops.
Configuration
# .valqore/notifications.yaml
channels:
- name: slack-platform
type: slack
webhook_url: ${VALQORE_SLACK_WEBHOOK}
events: [block, critical, drift, score_drop]
min_severity: high
environments: [production, staging]
- name: teams-security
type: teams
webhook_url: ${VALQORE_TEAMS_WEBHOOK}
events: [block, critical]
min_severity: critical
- name: jira-backlog
type: jira
base_url: https://your-org.atlassian.net
project_key: INFRA
issue_type: Bug
events: [block]
labels: ["valqore", "auto-created"]
- name: pagerduty-oncall
type: pagerduty
routing_key: ${VALQORE_PD_ROUTING_KEY}
events: [critical, triage]
min_severity: critical
- name: custom-webhook
type: webhook
url: https://hooks.example.com/valqore
method: POST
headers:
Authorization: "Bearer ${VALQORE_WEBHOOK_TOKEN}"
events: [block, critical, drift, triage, score_drop]Environment Variables
| Variable | Channel | Description |
|---|---|---|
VALQORE_SLACK_WEBHOOK | Slack | Slack incoming webhook URL. |
VALQORE_TEAMS_WEBHOOK | Teams | Microsoft Teams incoming webhook URL. |
VALQORE_JIRA_TOKEN | Jira | Jira API token. |
VALQORE_JIRA_EMAIL | Jira | Atlassian account email. |
VALQORE_PD_ROUTING_KEY | PagerDuty | PagerDuty Events API v2 routing key. |
VALQORE_WEBHOOK_TOKEN | Webhook | Bearer token for generic webhook auth. |
Filtering
Each channel supports:
- events -- list of event types to subscribe to.
- min_severity -- minimum finding severity to trigger notification.
- environments -- restrict to specific environments.
Was this helpful?