![[The AI Show Episode 142]: ChatGPT’s New Image Generator, Studio Ghibli Craze and Backlash, Gemini 2.5, OpenAI Academy, 4o Updates, Vibe Marketing & xAI Acquires X](https://www.marketingaiinstitute.com/hubfs/ep%20142%20cover.png)
![[FREE EBOOKS] The Kubernetes Bible, The Ultimate Linux Shell Scripting Guide & Four More Best Selling Titles](https://www.javacodegeeks.com/wp-content/uploads/2012/12/jcg-logo.jpg){kind=logo}
![From drop-out to software architect with Jason Lengstorf [Podcast #167]](https://cdn.hashnode.com/res/hashnode/image/upload/v1743796461357/f3d19cd7-e6f5-4d7c-8bfc-eb974bc8da68.png?#)
.png?#)
.jpg?#)
 (1).webp?#)
_Christophe_Coat_Alamy.jpg?#)
![Rapidus in Talks With Apple as It Accelerates Toward 2nm Chip Production [Report]](https://www.iclarified.com/images/news/96937/96937/96937-640.jpg)
Replace Opsgenie with this open-source alert router (save $2,280/year)
Tired of paying $199.5/month (10 users) for Opsgenie? Here’s how teams like yours are slashing costs by 90% while gaining full control over alert routing and templates using Versus Incident – an open-source alternative trusted by DevOps teams managing 10k+ servers. Why Teams Are Switching Feature Opsgenie Versus Incident Cost $2,280/year (10 users) Free Custom Templates Limited Go Templating Multi-Channel Routing Add-on Fees Built-in Lock-in Risk High None In this guide, you’ll learn how to route Prometheus Alertmanager alerts to Slack and Telegram using the Versus Incident, while fully customizing alert messages. Step 1: Redirect Alertmanager to Versus (5 Minutes) Update your alertmanager.yml to bypass Opsgenie’s webhook: route: receiver: 'versus-incident' group_wait: 10s # Faster than Opsgenie's 30s default! receivers: - name: 'versus-incident' webhook_configs: - url: 'http://versus-host:3000/api/incidents' send_resolved: true # Get resolution notices for free Step 2: Deploy Versus Incident (With Multi-Channel Fallback) Create a configuration folder: mkdir -p ./config Create a configuration file config/config.yaml: name: versus host: 0.0.0.0 port: 3000 alert: slack: enable: true token: ${SLACK_TOKEN} channel_id: ${SLACK_CHANNEL_ID} template_path: "/app/config/slack_message.tmpl" telegram: enable: true bot_token: ${TELEGRAM_BOT_TOKEN} chat_id: ${TELEGRAM_CHAT_ID} template_path: "/app/config/telegram_message.tmpl" docker-compose.yml – Always-on alerting with Slack + Telegram backup: version: '3.8' services: versus: image: ghcr.io/versuscontrol/versus-incident ports: - "3000:3000" volumes: - ./config:/app/config # Persist templates environment: SLACK_ENABLE: "true" SLACK_TOKEN: "xoxb-..." SLACK_CHANNEL_ID: "C123" TELEGRAM_ENABLE: "true" # Failover channel TELEGRAM_BOT_TOKEN: "123:ABC" TELEGRAM_CHAT_ID: "-456" Key Advantage: Unlike Opsgenie’s per-channel pricing, Versus lets you blast alerts to unlimited channels for $0. Step 3: Create Context-Rich Templates Slack Template (config/slack_message.tmpl):
Tired of paying $199.5/month (10 users) for Opsgenie? Here’s how teams like yours are slashing costs by 90% while gaining full control over alert routing and templates using Versus Incident – an open-source alternative trusted by DevOps teams managing 10k+ servers.
Why Teams Are Switching
| Feature | Opsgenie | Versus Incident |
|---|---|---|
| Cost | $2,280/year (10 users) | Free |
| Custom Templates | Limited | Go Templating |
| Multi-Channel Routing | Add-on Fees | Built-in |
| Lock-in Risk | High | None |
In this guide, you’ll learn how to route Prometheus Alertmanager alerts to Slack and Telegram using the Versus Incident, while fully customizing alert messages.
Step 1: Redirect Alertmanager to Versus (5 Minutes)
Update your alertmanager.yml to bypass Opsgenie’s webhook:
route:
receiver: 'versus-incident'
group_wait: 10s # Faster than Opsgenie's 30s default!
receivers:
- name: 'versus-incident'
webhook_configs:
- url: 'http://versus-host:3000/api/incidents'
send_resolved: true # Get resolution notices for free
Step 2: Deploy Versus Incident (With Multi-Channel Fallback)
Create a configuration folder:
mkdir -p ./config
Create a configuration file config/config.yaml:
name: versus
host: 0.0.0.0
port: 3000
alert:
slack:
enable: true
token: ${SLACK_TOKEN}
channel_id: ${SLACK_CHANNEL_ID}
template_path: "/app/config/slack_message.tmpl"
telegram:
enable: true
bot_token: ${TELEGRAM_BOT_TOKEN}
chat_id: ${TELEGRAM_CHAT_ID}
template_path: "/app/config/telegram_message.tmpl"
docker-compose.yml – Always-on alerting with Slack + Telegram backup:
version: '3.8'
services:
versus:
image: ghcr.io/versuscontrol/versus-incident
ports:
- "3000:3000"
volumes:
- ./config:/app/config # Persist templates
environment:
SLACK_ENABLE: "true"
SLACK_TOKEN: "xoxb-..."
SLACK_CHANNEL_ID: "C123"
TELEGRAM_ENABLE: "true" # Failover channel
TELEGRAM_BOT_TOKEN: "123:ABC"
TELEGRAM_CHAT_ID: "-456"
Key Advantage: Unlike Opsgenie’s per-channel pricing, Versus lets you blast alerts to unlimited channels for $0.
Step 3: Create Context-Rich Templates
Slack Template (config/slack_message.tmpl):
