PingTower checks your servers over HTTP/HTTPS, TCP, and ICMP, keeps latency history, and tells you the moment one goes down or comes back — in the browser, by email, or in Telegram.
| Probe | Evaluate | Store | Alert |
|---|---|---|---|
| Each server gets its own goroutine that checks it over HTTP/HTTPS, TCP, or ICMP on schedule | Failures in a row and slow responses flip a server to DOWN; a success brings it back UP |
Every ping — latency, RTT, packet loss, TLS, DNS — goes to ClickHouse in batches | Status changes reach the browser, email, and Telegram, with a cooldown against spam |

Monitoring events and notification delivery use RabbitMQ; the browser connects to the API over HTTP and SignalR.
| Product |
|---|
| api — REST API, live status SignalR hub, authentication, notification routing C# · ASP.NET Core 10 · MediatR · SignalR · EF Core · PostgreSQL |
| frontend — dashboard: servers, real-time statuses, latency charts, notification settings Vue 3 · TypeScript · Vite · Vue Router · Pinia · TanStack Vue Query · Reka UI · ECharts |
| Monitoring |
| ping-service — HTTP/HTTPS, TCP and ICMP probes, one goroutine per target Go · pro-bing · RabbitMQ · Redis |
state-elevator — status lifecycle: failure and latency thresholds → UP / DOWNC# · .NET Worker Service · RabbitMQ · Redis |
| metrics-writer — batched ping history writes to ClickHouse C# · .NET Worker Service · ClickHouse |
| Notifications |
| email-service — SMTP email with retries and a circuit breaker C# · .NET Worker Service · MailKit · Polly |
| tg-bot — Telegram bot: welcome flow and alert delivery; account linking is verified by the API Python · FastAPI · aiogram · FastStream |
| Platform |
| specs — system guide: service interactions, event flows, data ownership, API integration and troubleshooting Markdown · Mermaid · Links to implementation and deployment sources |
| infra — shared PostgreSQL, Redis, ClickHouse and RabbitMQ; production manifests and a local stack Makefile Kubernetes / k3s · GitLab Agent · External Secrets · Docker Compose for local development |
| I want to… | Go to |
|---|---|
| try the running app | pingtower.tech — registration, monitors, notification settings and Telegram integration |
| deploy to Kubernetes | deployment guide — manifests, CI/CD and required variables |
| run everything locally | infra: make -C infra up — storages, broker, migrations and all services |
| understand how services fit together | service map — responsibilities, storage and connections |
| understand the event flow | event flows and contracts — from one check to a status update and alert |
| integrate over REST | integration guide — authentication, request examples, errors and SignalR; OpenAPI for endpoint schemas |
| diagnose a failure | troubleshooting — protocol checks, event delivery and runtime dependencies |
