b2b-backend-monitor

Plan-based production log monitoring automates post-release health checks by reading a plan file to extract keywords, environment overrides, and collection cadence. It continuously polls Elastic Beanstalk or ECS deployment status and outputs structured reports with warnings and escalation prompts.

Real-time log polling after ECS deployments watches production environments by tracking configured keywords from your test plan. It automatically collects logs and generates structured reports containing specific warnings and escalation prompts for any detected issues.

Yes, plan-driven log monitoring reads the api-test-plan file directly to extract monitoring settings, environment overrides, keywords, and collection cadence. This configures automated real-time polling and health checks for production Elastic Beanstalk and ECS deployments.

Automated log monitoring explicitly avoids running during plan creation, plan updates, or active troubleshooting. It is scoped strictly to post-release log collection and real-time polling of production environments to prevent interference with other deployment workflows.

Start monitoring by specifying the environment and plan file path, such as running the monitor command against prod with your deploy plan markdown file. The system reads the configuration to track EB or ECS deployment status and outputs structured health reports.