azirar/glenn repository overview

⁠Glenn - Health Monitoring Platform

A reactive health monitoring platform

⁠📋 Overview

Glenn is a reactive health monitoring platform that continuously checks the availability and performance of your applications. Named after the dedicated healer from the light novel "Monster Girl Doctor," Glenn watches over your digital ecosystem with the same care and attention.

⁠✨ Key Features

• 🔄 Continuous Monitoring: Automatically checks your applications at configurable intervals
• 📊 Real-time Dashboard: Live view of all monitored applications with status indicators
• ⚡ Reactive Architecture: Built with Spring WebFlux and R2DBC for non-blocking operations
• 📈 Response Time Tracking: Monitor performance metrics over time
• 🏷️ Category Management: Organize applications by categories with filtering
• 📱 Responsive Design: Works on desktop and mobile devices
• 🔔 Status History: Complete history of all health checks
• ⚙️ Configurable Status Codes: Define which HTTP codes indicate a healthy application
• 🌐 Live Updates: Server-Sent Events (SSE) for real-time dashboard updates

⁠🏗️ Architecture

Glenn is built with a modern reactive stack:

• Backend: Spring Boot 3.3.2 with WebFlux
• Database: PostgreSQL with R2DBC for reactive data access
• Migrations: Liquibase for database schema management
• Frontend: Thymeleaf with Bootstrap 5 and Chart.js
• Real-time: Server-Sent Events (SSE) for live updates
• Build Tool: Maven

⁠🚀 Getting Started

⁠Prerequisites

• Java 21 or higher
• PostgreSQL 14 or higher
• Maven 3.8+

⁠Installation

1. Clone the repository

   git clone https://github.com/AZIRARM/Glenn.git
   cd glenn
   

   Copy

2. Configure the database

   Create a PostgreSQL database:

   CREATE DATABASE glenn;
   

   Copy

3. Configure environment variables

   Create a .env file at the project root:

   POSTGRES_URL=jdbc:postgresql://localhost:5432/glenn
   POSTGRES_REACTIVE_URL=r2dbc:postgresql://localhost:5432/glenn
   POSTGRES_USERNAME=postgres
   POSTGRES_PWD=yourpassword
   

   Copy

4. Build the application

   mvn clean package
   

   Copy

5. Run the application

   mvn spring-boot:run
   

   Copy

   Or with environment variables:

   set -a; source .env; set +a; mvn spring-boot:run
   

   Copy

6. Access the dashboard

   Open your browser and navigate to http://localhost:1080

⁠📖 Usage Guide

⁠Adding an Application

1. Click the "Add Application" button on the dashboard
2. Fill in the application details:
   • Name: A descriptive name (e.g., "Production API")
   • Category: Optional category for filtering (e.g., "Backend", "Frontend")
   • Description: Optional description of the application's purpose
   • URL: The endpoint to monitor (must start with http:// or https://)
3. Select which HTTP status codes indicate a healthy application
   • Use preset buttons for quick selection (2xx Success, 3xx Redirect)
   • Default selection includes common success codes
4. Click "Add Application" to start monitoring

⁠Dashboard Features

• Status Cards: Visual cards showing application name, current status, response time, and HTTP code
• Statistics Bar: Overview of total apps, healthy/unhealthy counts, and global uptime
• Category Filtering: Click on category badges to filter applications by category
• Status Filtering: Filter by all, healthy, or unhealthy applications
• Live Updates: Dashboard updates automatically when new health checks are performed
• Quick Actions: Pause/resume monitoring or delete applications directly from the dashboard

⁠Application Details

Click the "Details" button on any application card to access:

• Complete application information
• Uptime statistics (24h, 7d, 30d)
• Response time chart
• Complete status history
• Edit application configuration

⁠Editing an Application

Click the pencil icon (✏️) on an application card or in the details view to:

• Modify application name, category, or description
• Update the monitored URL
• Change accepted status codes

⁠⚙️ Configuration

⁠Application Properties

⁠Monitoring Configuration

The monitoring service automatically:

• Checks all active applications at the configured interval
• Records status, response time, and any errors
• Updates the dashboard in real-time via SSE
• Maintains complete history for uptime calculations

⁠🛠️ Technology Stack

⁠📁 Project Structure

glenn/
├── src/
│   ├── main/
│   │   ├── java/org/azirar/glenn/
│   │   │   ├── endpoints/        # Web controllers
│   │   │   ├── handlers/         # Business logic
│   │   │   ├── models/           # Domain entities
│   │   │   └── repositories/     # Data access
│   │   └── resources/
│   │       ├── db/changelog/     # Liquibase migrations
│   │       ├── static/           # CSS, JS, images
│   │       ├── templates/        # Thymeleaf templates
│   │       └── application.yml   # Application config
│   └── test/                     # Unit tests
├── pom.xml                        # Maven configuration
└── README.md                      # This file

⁠🌟 Why "Glenn"?

Glenn is named after the compassionate healer from the light novel and anime "Monster Girl Doctor." Just as Glenn treats and cares for monster girls with dedication and expertise, this platform monitors and cares for your applications, ensuring they stay healthy and performant.

⁠📊 Roadmap

• Basic health monitoring
• Real-time dashboard with SSE
• Category filtering
• Response time tracking
• Application editing
• Email/Slack notifications
• Advanced uptime SLAs
• Custom monitoring intervals per application
• API for external integrations
• Prometheus metrics export
• Grafana dashboards

⁠🤝 Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

1. Fork the repository
2. Create your feature branch (git checkout -b feature/amazing-feature)
3. Commit your changes (git commit -m 'Add some amazing feature')
4. Push to the branch (git push origin feature/amazing-feature)
5. Open a Pull Request

⁠📝 License

This project is licensed under the GNU GENERAL PUBLIC LICENSE - see the LICENSE file for details.

⁠👏 Acknowledgments

• Inspired by the need for simple, reactive health monitoring
• Named after Glenn Litbeit from "Monster Girl Doctor" (Kensuke Koba)
• Built with Spring Boot and the amazing Java ecosystem

⁠Glenn vs Other Monitoring Solutions

⁠Why Glenn Stands Out

⁠🎯 Perfect for Java Developers

⁠📊 Performance & Scalability

⁠🚀 What Makes Glenn Unique

⁠1. Stream Protocol Support

Unlike competitors limited to HTTP/HTTPS, Glenn monitors:

• PostgreSQL databases
• MySQL/MariaDB
• MongoDB
• SSH services
• Redis instances
• RabbitMQ/AMQP

⁠2. Enterprise-Grade Database

• PostgreSQL persistence means:
  • Years of history
  • Complex queries
  • Data integrity
  • Backup/restore capabilities

⁠3. Reactive from the Core

• Spring WebFlux + R2DBC = truly non-blocking
• Handles thousands of concurrent checks
• Efficient resource usage
• Perfect for microservices environments

⁠4. Developer-Friendly

• Pure Java - easy to extend
• Familiar Spring ecosystem
• Clean, maintainable codebase
• Perfect for teams already using Java

⁠📈 Ideal Use Cases

⁠🎓 Comparison Summary

⁠💡 When to Choose Glenn

• ✅ You're a Java/Spring developer
• ✅ You need to monitor databases and services, not just HTTP
• ✅ You want long-term history in PostgreSQL
• ✅ You prefer self-hosted solutions
• ✅ You need a lightweight but powerful monitoring tool

⁠🔮 Future Potential

Glenn isn't just another uptime monitor. It's a modern, reactive health monitoring platform built for Java developers who need more than just HTTP checks.

⁠📧 Contact

Project Link: Glenn on Github⁠