Skip to content

Implement service health monitoring and incident tracking platform - #1

Draft
camjaycecamp with Copilot wants to merge 5 commits into
mainfrom
copilot/create-service-health-tracking
Draft

Implement service health monitoring and incident tracking platform#1
camjaycecamp with Copilot wants to merge 5 commits into
mainfrom
copilot/create-service-health-tracking

Conversation

Copilot AI commented Jan 26, 2026

Copy link
Copy Markdown

Full-stack platform for monitoring service health with automated checks, alert generation, and incident lifecycle management. Built as modular codebase (React + Spring Boot + PostgreSQL) with containerized deployment.

Backend (Spring Boot 3.2)

  • Entities: Service, HealthCheck, Alert, Incident, Runbook with JPA relationships
  • Scheduled health checks: HTTP monitoring with configurable intervals (default 60s), automatic status updates
  • Alert lifecycle: Auto-generation on failures with severity mapping (DOWN→CRITICAL, DEGRADED→HIGH)
  • Incident tracking: Status progression from OPEN through ACKNOWLEDGED, INVESTIGATING to RESOLVED/CLOSED
  • REST API: Standard CRUD endpoints for all entities with service-specific queries
@Scheduled(fixedDelayString = "${incidentops.health-check.interval:60000}")
public void performScheduledHealthChecks() {
    List<Service> services = serviceService.getAllServices();
    services.forEach(service -> {
        HealthCheck check = healthCheckService.performHealthCheck(service);
        if (check.getStatus() == FAILURE) {
            alertService.createAlertForService(service, check.getErrorMessage());
        }
    });
}

Frontend (React 18)

  • Dashboard: Aggregated health metrics and recent alerts/incidents
  • Service management: CRUD with health check history viewer
  • Alert management: Acknowledge/resolve workflow with severity filtering
  • Incident tracking: Status transitions with optional runbook association
  • Runbook library: Searchable resolution guides with markdown content

Infrastructure

  • PostgreSQL schema: Indexed foreign keys, cascading deletes on service removal
  • Docker Compose: Three-service setup (postgres, backend, frontend) with health checks
  • Sample data: Pre-configured services hitting public APIs for immediate testing
  • Scripts: start.sh for Docker deployment, setup-dev.sh for local development

Quality

  • H2 in-memory DB for test isolation
  • Timeout validation with @PostConstruct to fail fast on misconfiguration
  • ARIA attributes on modals for accessibility
  • CodeQL scan clean
Original prompt

Personal portfolio computer science project for learning full-stack development. A lightweight service-health and incident tracking platform. It runs scheduled health checks, generates alerts, and tracks incident lifecycle with runbooks. Currently built to function as a modular codebase (React + Java API + Postgres) with future plans to introduce distributed worker and cloud deployment features.


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Copilot AI and others added 4 commits January 26, 2026 23:17
…ing Boot backend, and PostgreSQL database

Co-authored-by: camjaycecamp <82195306+camjaycecamp@users.noreply.github.com>
Co-authored-by: camjaycecamp <82195306+camjaycecamp@users.noreply.github.com>
Co-authored-by: camjaycecamp <82195306+camjaycecamp@users.noreply.github.com>
…ssibility improvements

Co-authored-by: camjaycecamp <82195306+camjaycecamp@users.noreply.github.com>
Copilot AI changed the title [WIP] Add modular service health and incident tracking platform Implement service health monitoring and incident tracking platform Jan 26, 2026
Copilot AI requested a review from camjaycecamp January 26, 2026 23:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants