Why monitor business processes
A growing platform needs to see its business processes, not just its servers. As an e-commerce platform grows, so does the number of processes around it: payment providers, ERP exchange, SMS and email notifications, product and price feeds, scheduled jobs.
Classic infrastructure monitoring shows whether the servers are healthy. A growing business also needs to know whether orders reach the ERP, whether customers get their notifications and whether feeds are up to date. WebbyLab adds a business layer to monitoring, so the technical and business teams see the platform the same way and get the right signal in time.
What the system does: six capabilities in one system
- One picture of every signal. Infrastructure, application and business metrics, logs and alerts in one place, with 30 days of history.
- Performance of every endpoint. CPU time and latency per route show which parts of the platform cost the most and why, with minimal changes to the application.
- Business metrics. Orders, payments, ERP exchange, customer notifications, the catalogue and feeds, read safely on a schedule.
- Alerts for the right people. Routine ones go to the team chat, critical ones ring a phone. Grouped, deduplicated and covered by automated tests.
- Secure by default. Dashboards behind a zero-trust gateway, no new inbound connections to production, least privilege everywhere.
- Ready for AI agents. Engineers ask questions about production in plain language; the agent reads the same data as the dashboards, read-only.
How it works: from data sources to answers
Agents collect what the platform already has, business queries add the state of key processes, and one monitoring platform turns it all into dashboards, alerts and answers for AI agents.
How we implement it
- Start with business questions. Which processes matter most and what counts as a problem for each.
- Open stack. Prometheus, Loki, Grafana, Alertmanager and Grafana Alloy: no per-server or per-gigabyte fees, data stays in the client’s infrastructure.
- Safe for production. Agents push data out; every database query is measured before launch and runs on a schedule with a time limit.
- Everything as code. Configuration in git, every change reviewed, no vendor lock-in.
- Fast start, then tuning. First findings within 48 hours of data arriving, then alert thresholds are tuned on real data.
What the business gets
- Faster detection (minutes). Critical problems raise an alert within minutes, and the team acts before customers notice.
- Faster releases (same evening). Release problems are diagnosed within minutes on the same dashboards and fixed quickly.
- Capacity planned on data (weeks ahead). A warning arrives weeks before resources run short; customer traffic is separated from bots.
- Answers in seconds (30 min → 10 s). Operational questions that took half an hour by hand take about ten seconds in one panel.
A fraction of the SaaS cost
Savings of ≈ $5.5–8k a year at the volumes of a large e-commerce platform, with no per-user fees.
* Example from the Brain implementation (≈280 million log lines a month). SaaS estimate based on published infrastructure and log monitoring prices; actual offers may differ.
Who it is for
- E-commerce and retail. Platforms with payments, ERP exchange, feeds and customer notifications.
- Growing platforms. Teams that need to plan capacity and releases on data.
- Teams with AI agents. Companies that want to give AI agents safe access to production data.
The same system at Brain
Brain is a Ukrainian chain of computer and electronics stores whose website offers a much wider range of products. WebbyLab has worked with Brain before on its B2B portal for dealers.
- 48 hours: first findings. Business metrics surfaced four issues the team then resolved: notifications stuck in a queue, the reviews feed, a nightly job and SMS delivery delays.
- Minutes: release diagnosis. A release problem was identified within minutes and fixed the same evening.
- ~10 min: SMS and ERP under control. SMS delivery and ERP exchange raise an alert in about ten minutes.
- 3 of 3: ERP alert with no false alarms. Tested on 30 days of history, the ERP alert caught all three real incidents.
- 55 → 6 min: a fresh catalogue every morning. The nightly catalogue update was optimised from 50–55 minutes to 6.
- ≈ $85 / month: cost. For the whole stack, versus an estimated $545–770 for SaaS monitoring at the same volumes.
Technology stack
- Metrics and logs: Prometheus, Loki
- Alerting: Alertmanager, automated rule tests
- Data collection: Grafana Alloy, SQL exporter
- Dashboards: Grafana
- Platform: Kubernetes, infrastructure as code
- AI agents: Claude via MCP (read-only)
WebbyLab expertise
- Monitoring architecture: metrics, logs and business data in one cost-efficient stack.
- Business monitoring: orders, payments and integrations as metrics and alerts.
- Secure by default: zero-trust access and least privilege for every component.
- Reliable alerting: routed, deduplicated rules, tested on history.
- AI agent integration: read-only access for plain-language questions.
- Infrastructure as code: reviewed, reproducible, no vendor lock-in. This is the work of our DevOps team.
Dashboards are for people. The same data behind a read-only door is for AI agents.