post-deployment-monitor

Correlate Kubernetes code diffs with Grafana metrics to generate health reports.

31|4|Updated Aug 24, 2021
One-click install
npx skills add https://github.com/razorpay/trino-gateway --skill post-deployment-monitor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-deployment-monitor
Source: https://github.com/razorpay/trino-gateway/tree/main/.agents/skills/post-deployment-monitor
Command: npx skills add https://github.com/razorpay/trino-gateway --skill post-deployment-monitor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Monitor Kubernetes deployments after release by correlating code changes with production observability metrics to detect regressions and performance issues.

Core Features & Use Cases

  • Load and apply repository skills to identify affected flows and endpoints.
  • Build and validate Grafana queries against deployment time boundaries to generate comprehensive health reports.
  • Orchestrate a multi-phase workflow that analyzes code diffs, loads skills, and produces a deterministic health assessment.

Quick Start

Generate a post-deployment health report by supplying deployment name, namespace, and cluster.

Frequently Asked Questions about post-deployment-monitor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Kubernetes post-deployment health checks?

Automate Kubernetes post-deployment health checks by correlating code diffs with observability metrics to generate a structured health report. This process retrieves deployment images, analyzes commit diffs, and validates Grafana metrics against deployment time boundaries.

How do I correlate code changes with Grafana metrics after a deployment?

Correlate code changes with Grafana metrics by building and validating queries against deployment time boundaries. The workflow analyzes complete commit diffs across all commits, loads repository skills to map changes to flows, and validates metrics to detect regressions.

Can I monitor deployments across multiple Kubernetes clusters and namespaces?

You can monitor deployments across multiple Kubernetes clusters and namespaces. The health monitoring workflow applies to Kubernetes deployments across your infrastructure, enabling full lifecycle support from diff loading to metric validation for multiple flows.

What is the best way to detect performance regressions after a Kubernetes release?

The best way to detect performance regressions is by correlating code changes with production observability metrics. This approach retrieves deployment images, analyzes complete commit diffs, and validates metrics against deployment-time boundaries to produce a deterministic health assessment.

Do I need repository skills to map code changes to affected flows?

You need repository skills to map code changes to affected flows and endpoints. The workflow loads and applies these skills to identify impacted areas, then orchestrates a multi-phase process that analyzes code diffs and produces a structured health assessment.