Application Services
Prom2Teams
Chkk coverage for Prom2Teams. We provide preflight/postflight checks, curated release notes, and Upgrade Templates—designed for seamless upgrades.
Coverage Matrix
| Chkk Curated Release Notes | v3.2.0 to latest |
| Private Registry | Supported |
| Custom Built Images | Supported |
| Safety, Health, and Readiness Checks | v3.3.0 to latest |
| Supported Packages | Helm, Kustomize, Kube |
| EOL Information | Available |
| Version Incompatibility Information | Available |
| Upgrade Templates | In-Place, Blue-Green |
| Preverification | Available |
Prom2Teams Overview
Prom2Teams is an open-source webhook receiver bridging Prometheus Alertmanager and Microsoft Teams, enabling real-time delivery of monitoring alerts directly into Teams channels. It converts Alertmanager JSON payloads into formatted Teams messages, grouping multiple alerts and filtering unnecessary details. Prom2Teams manages alert retries automatically, ensuring reliable notifications even under intermittent connectivity issues. This centralized integration simplifies the alerting pipeline, removing the need for custom scripts or plugins in your observability stack.Chkk Coverage
Curated Release Notes
Chkk curates Prom2Teams release notes, highlighting significant updates, deprecated features, and critical configuration changes relevant to your deployment. It flags essential updates such as Teams webhook schema changes—like the transition to Adaptive Card workflows—that could impact alert delivery. Chkk provides concise insights, enabling quick assessment of operational impacts without needing to parse through extensive GitHub logs. By contextualizing updates, Chkk ensures you know exactly when and why an upgrade matters.Preflight & Postflight Checks
Chkk runs preflight checks on your Prom2Teams setup before upgrades, verifying compatibility with the target version and ensuring key configurations—such as webhook endpoints—are correct. It alerts you to deprecated fields or misconfigured connector URLs that could disrupt alert flow. Post-upgrade checks validate successful notification routing, scanning logs and metrics for delivery failures or formatting issues. These automated validations help identify critical issues immediately, minimizing downtime and ensuring alerts reliably reach Teams.Version Recommendations
Chkk tracks Prom2Teams versions and proactively alerts you when your deployed version falls out of maintenance—particularly around events like Microsoft’s deprecation of legacy webhook formats. It recommends stable upgrade paths, aligning version suggestions with community feedback and known operational stability. This approach ensures your Prom2Teams deployment consistently supports required features, such as adaptive card workflows, to maintain uninterrupted alerting. Custom internal builds or forks are also supported, allowing tailored guidance based on your specific environment.Upgrade Templates
Chkk provides detailed Upgrade Templates covering both in-place and blue-green upgrade strategies for Prom2Teams. In-place templates guide you step-by-step through safely updating your existing deployment while ensuring alert continuity. Blue-green templates detail running parallel Prom2Teams instances, enabling gradual validation of the new deployment with low-risk alerts before switching fully. These templates integrate seamlessly into your existing GitOps or CI/CD workflows, ensuring consistent upgrades with built-in rollback points.Preverification
Preverification simulates Prom2Teams upgrades in an isolated environment, mirroring your actual setup to detect potential issues before production deployment. Chkk tests alert processing, payload compatibility, and endpoint connectivity with representative alert payloads. By surfacing configuration or connectivity problems early—such as schema mismatches or endpoint changes—preverification ensures issues are resolved beforehand. This process significantly reduces production risks, ensuring smooth Prom2Teams upgrades with minimal operational impact.Supported Packages
Chkk supports all common Prom2Teams deployment methods, including Helm charts, Kubernetes manifests (YAML/Kustomize), and standalone Docker deployments. It seamlessly integrates into your existing deployment approach, adapting upgrade recommendations to your specific packaging and repository management practices. Custom configurations, such as private container registries, or modified Helm values, are recognized and incorporated. This flexibility allows Chkk to deliver accurate, actionable upgrade guidance tailored specifically to your Prom2Teams environment.Common Operational Considerations
- Alertmanager Webhook Mismatch: Incorrect webhook URLs (e.g., old “Connector” endpoint) cause silent notification failures. Always update Alertmanager receiver URLs to match Prom2Teams connector paths precisely.
- Teams Connector Deprecation: Legacy Teams webhooks are deprecated; versions below Prom2Teams 5.0.0 fail silently. Upgrade promptly to ensure compatibility with Microsoft’s new Adaptive Card-based workflow.
- Single-Instance Risk: A single Prom2Teams instance creates a critical failure point; use at least two replicas behind a Kubernetes Service. Load balancing ensures continuous alert delivery even if one instance fails.
- Custom Template Compatibility: After upgrades, custom Jinja2 templates may become outdated, causing missing or malformed fields in Teams messages. Review templates against new release notes and test alerts thoroughly.
- Monitoring Delivery Failures: Prom2Teams metrics should be monitored closely for increased HTTP errors or dropped alerts. Set Prometheus alerts to detect and respond proactively to Teams webhook delivery issues.
- Alert Volume and Rate Limits: Large alert bursts can trigger Teams webhook rate limits or truncated messages. Tune Alertmanager grouping and routing rules to aggregate alerts effectively and avoid notification throttling.