Task: Develop and add website performance and operation monitoring

Objective

Add a lightweight observability system for the website to quickly understand:

• whether the website and its key services are running;
• where errors occur;
• how performance is changing;
• whether there is degradation in response time, load, or resources.

Constraints and Preferences

• Do not use Sentry as the primary tool.
• Avoid heavy and redundant infrastructure.
• Preference for simple, clear, and inexpensive/self-hosted solutions.
• Consider a structured logs + Prometheus + Grafana stack and lighter alternatives if they solve the task more simply.

What to Develop

1. Determine the minimum set of observability for the current website architecture.
2. Configure centralized collection and convenient viewing of application/web server logs.
3. Add metrics at least for:
   • availability;
   • HTTP status / error rate;
   • latency / response time;
   • request rate;
   • CPU, RAM, disk, and other important host/container resources, if applicable.
4. Add application metrics for critical website operations if necessary.
5. Build a compact health and performance dashboard.
6. Add basic alerts for critical failure states and noticeable degradation.
7. Check the impact of monitoring itself on resources and prevent unjustified operational complexity.

Candidates

Baseline option for evaluation:

• structured application/web server logs;
• Prometheus;
• exporters / application with /metrics;
• Grafana;
• lightweight log backend (e.g., Loki or equivalent) if necessary and justified.

A simpler stack is acceptable if it provides sufficient diagnosability and lower operational costs.

Deliverables

• minimum monitoring stack selected and justified;
• monitoring deployed and connected to the website;
• logs and main metrics available;
• dashboard with key performance indicators available;
• minimum necessary alerts configured;
• documentation on where to check system health and how to diagnose typical issues.