SLA Monitoring Setup for Web Applications

Your fintech web app crashes at 3 AM, SLA promises 99.9%, and a monitoring configuration error costs you the contract. Real case: a client was losing up to 5% of users per downtime until we set up correct SLI and burn-rate alerts. SLA monitoring is not just an uptime checker; it's a system for measuring and managing reliability. We configure it turnkey for web applications of any complexity. With 10+ years of experience and over 50 monitoring projects, our certified engineers ensure metric transparency and timely notifications. If you don't know how to track SLA compliance or want to automate alerts, contact us for a consultation.

Which Metrics to Track in SLA

SLA (Service Level Agreement) defines target indicators. Availability (uptime) formula: (total_time - downtime) / total_time * 100%. For 99.9% SLA, allowed downtime is ~8.7 hours per year; for 99.99%, it's 52 minutes.

Response Time — P95 and P99 matter more than average: the average hides the tail of slow requests. Typical targets: P95 < 500ms, P99 < 2s.

Error Rate — percentage of 5xx errors — target < 0.1% for production.

How to Set Up SLA Monitoring with Prometheus

1. Define SLI (Service Level Indicators): uptime, P95/P99 latency, error rate, throughput.
2. Formulate SLO (Service Level Objectives): 99.9% uptime, P95 < 500ms, errors < 0.1%.
3. Write Prometheus rules for SLI/SLO calculation and burn-rate alerts.

# Rule for availability SLO (target: 99.9%)
- record: job:availability:ratio_rate5m
  expr: |
    1 - (
      rate(http_requests_total{status=~"5.."}[5m])
      /
      rate(http_requests_total[5m])
    )

# Alert: SLO at risk (burn rate > 14.4x over 1 hour)
- alert: SLOBurnRateTooHigh
  expr: |
    job:availability:ratio_rate5m < 0.999
    and
    rate(http_requests_total{status=~"5.."}[1h]) > 0
  for: 2m
  labels:
    severity: critical
  annotations:
    summary: "SLO availability at risk"

4. Configure a Grafana dashboard to visualize SLO, error budget, and burn rate.
5. Add external checks (Pingdom, Blackbox Exporter) from different geographic locations.

How to Choose a Metric Collection Tool

Prometheus + Grafana gives full control and saves budget but requires a DevOps engineer for maintenance. Datadog is easier to deploy, but costs grow significantly with metric volume — Prometheus can handle 5x more metrics on the same hardware. External monitors like Uptime Robot are a lightweight addition but don't replace internal metrics. The choice depends on data volume and budget.

Why Error Budget Matters

Error budget is the allowable downtime over a period (e.g., 43 minutes per month for 99.9% SLO). It balances reliability and development speed: if the budget is not exhausted, you can ship features faster; if exhausted, reliability takes priority. We configure automatic error budget calculation in Grafana and alerts when it is depleted. According to Site Reliability Engineering from Google, error budget enables informed release decisions.

One of the most common mistakes is setting overly strict SLO without considering infrastructure cost. For example, demanding 99.99% availability for an internal service can increase costs 2–3 times without tangible benefit. Another mistake is lack of metric validation: if Prometheus is not scraping the correct endpoint, SLA becomes a fiction. We recommend starting with 99.9% and adjusting based on data.

What's Included in SLA Monitoring Setup

• Installation and configuration of Prometheus, Grafana, Alertmanager (on your infrastructure or cloud)
• Defining SLI/SLO and burn-rate alerts
• Dashboard with SLO, error budget, trends
• External checks (Uptime Robot or Blackbox Exporter)
• Automatic monthly reporting (PDF)
• Monitoring documentation
• Access to dashboards and alerts
• Team training (1 hour)
• 2 weeks support after delivery

We have been on the market for over 5 years, completed 50+ monitoring projects. We use only proven stacks, guarantee engineer response SLA of 1 hour. Get a consultation — write to us. Order turnkey SLA monitoring setup.

SLA Reporting

Automatic monthly report for business: actual uptime vs target, incident list, error budget usage, trend. Grafana generates PDF on schedule; for enterprise, Datadog SLO Reports.

Setup Timeline

Total timeline: from 5 to 8 working days depending on system complexity.

We regularly encounter a situation: "The site is not opening" at 3 a.m. — and it turns out that the VPS disk is full because nginx logs haven't been rotated for six months. Or the server went down under load on the day of an advertising campaign launch because the shared hosting had a limit of 50 concurrent connections. Setting up hosting and deployment is not about "where it's cheaper" but about what happens when something goes wrong. Our team helps avoid such incidents by designing infrastructure that accounts for real load patterns.

When to choose Vercel and Netlify?

Vercel is built for Next.js — deploy in one push, preview deployments for every PR, automatic CDN, Edge Functions, ISR without configuration. For frontend projects and JAMstack, it's the optimal choice: no operational overhead, time-to-deploy measured in minutes.

Real limitations: Vercel Serverless Functions run in us-east-1 by default (latency for Europe +80–100ms), Function timeout 300 seconds on Pro, Bandwidth 1TB/month on Pro. For heavy backend, you need workers or a separate server.

Netlify is closer to static sites and Edge Functions based on Deno Deploy. Build minutes are the main limitation on the free tier.

Why is Docker the foundation of predictable deployment?

"It works on my machine" — classic. Docker solves this through environment containerization. But a bad Dockerfile creates new problems.

A typical mistake: copying everything into the image without .dockerignore, resulting in an 800MB image instead of 80MB. node_modules inside the image weighs as much. Correct approach: multi-stage build.

FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY . .
RUN npm run build

FROM node:20-alpine AS runner
WORKDIR /app
COPY --from=builder /app/.next ./.next
COPY --from=builder /app/node_modules ./node_modules
COPY --from=builder /app/package.json ./package.json
EXPOSE 3000
CMD ["npm", "start"]

Final image: 180MB instead of 1.2GB. CI build time is reduced due to layer caching — if package.json hasn't changed, the layer with npm ci is taken from cache.

Docker Compose for local development and simple production scenarios: application + PostgreSQL + Redis in one configuration. For production on a single server, it's a perfectly viable option if there's no requirement for horizontal scaling.

More about containerization — Wikipedia: Docker.

How to set up Nginx as a reverse proxy?

Nginx in front of the application is standard for VPS and dedicated servers. Main functions: SSL termination, gzip, static files, rate limiting, upstream load balancing.

A configuration often done incorrectly: worker_processes auto — number of processes equals CPU count. worker_connections 1024 — that's 1024 per worker process. With 4 CPUs and 1024 connections = 4096 concurrent connections. For a high-traffic site, you need worker_connections 4096 and set keepalive_timeout 65.

For static assets with hash in the filename:

location ~* \.(js|css|woff2|png|webp)$ {
    expires 1y;
    add_header Cache-Control "public, immutable";
}

immutable tells the browser: don't revalidate this file even on hard refresh. This only works correctly with content-hashed filenames (which Vite/webpack do by default). Documentation — Wikipedia: Nginx.

AWS: flexibility and complexity

EC2 + Auto Scaling Group — classic for horizontal scaling. AMI with pre-installed application, Launch Template, ASG with min/desired/max instances, Application Load Balancer. When CPU > 70% for 3 minutes — scale out, when CPU < 30% for 15 minutes — scale in. Health check via ALB removes unhealthy instances from rotation.

ECS Fargate — containers without managing EC2. Deploy a Docker image, specify CPU/memory (512 CPU units = 0.5 vCPU, from 512MB memory), Fargate launches it. More expensive than Lambda, but no cold start and no timeout limitations. Suitable for long-running processes, WebSocket servers, heavy workers.

RDS for PostgreSQL with Multi-AZ: automatic failover in 1–2 minutes when primary fails. Read Replicas for scaling reads. RDS Proxy for connection pooling — Lambda functions cannot hold long-term connections, the proxy buffers this.

Kubernetes: when it is justified

K8s adds significant operational complexity. Justified when: multiple teams deploy independent services, fine-grained resource allocation per service is needed, canary deployments and blue/green without downtime are required.

AWS EKS, GKE, or managed k8s from Hetzner (cheaper). Helm charts for standard services. Horizontal Pod Autoscaler based on CPU and custom metrics (RPS via Prometheus).

For most startups and medium-sized projects, Kubernetes is overkill. ECS or Fly.io provide 80% of the capabilities with 20% of the operational complexity.

Monitoring and alerting

A server without monitoring is waiting for an incident. Minimal stack: Prometheus + Grafana (or Grafana Cloud for managed), alerting on disk > 80%, memory > 85%, CPU > 90% over 5 minutes, error rate > 1%. Uptime via Better Uptime or Upptime (self-hosted).

Logs: Loki + Grafana or CloudWatch Logs Insights. Structured JSON logs (winston, pino) are mandatory — otherwise, log searching becomes a pain.

What is included in hosting setup

• Audit of current infrastructure and load profiling
• Selection of target architecture (VPS, AWS, serverless, Kubernetes)
• Setting up CI/CD pipeline (GitHub Actions, GitLab CI) with automatic deployment
• IaC via Terraform or Pulumi (infrastructure as code)
• Configuration of Nginx, SSL certificates, HTTP/2, brotli
• Monitoring and alerting (Prometheus + Grafana, PagerDuty)
• Documentation of runbooks and team training

Additionally, contact us if you need migration from current hosting or integration with external services.

Work process

1. Audit of current infrastructure (2–5 days)
2. Selection of target architecture with load and budget justification (1–3 days)
3. Setting up CI/CD pipeline (GitHub Actions, GitLab CI) (2–5 days)
4. IaC via Terraform or Pulumi (3–10 days)
5. Setting up monitoring and alerting (2–5 days)
6. Documentation of runbooks and team training (1–3 days)

Our experience — 7 years on the market, over 50 projects, guarantee of operability after deployment.

Timeline

• Basic deployment on VPS with Docker + Nginx + CI/CD: 1–2 weeks.
• Setting up AWS infrastructure with Auto Scaling, RDS, CDN: 3–6 weeks.
• Migration to EKS from scratch: 6–12 weeks.
• Setting up Vercel/Netlify for JAMstack: 3–5 days.

The cost is calculated individually depending on complexity and scope of work. Get a consultation — we'll evaluate your architecture in one day.