Production-Ready Zabbix Monitoring Setup for Websites

Standard Zabbix installation from tutorials generates hundreds of triggers that create noise and miss real failures. After attaching a pre-built Linux by Zabbix agent template, each server gets 200+ triggers—half fire constantly, while critical incidents go unnoticed. We solve this by setting up production-ready monitoring: deliberate architecture, clear metrics, and sensible thresholds. Over 6 years, we have saved clients more than 5 million rubles (approx. $55,000) on infrastructure through monitoring optimization, and reduced total false alarms by 80%.

This article covers: Zabbix server setup, Zabbix server monitoring, Zabbix production deployment, Zabbix triggers, monitoring templates, Zabbix web scenarios, Zabbix Telegram notifications, Zabbix storage optimization, TimescaleDB Zabbix integration, Zabbix proxy architecture, custom Zabbix templates, and web application monitoring.

Choosing a Zabbix Deployment Scheme

For a single site with a few servers, use Zabbix Server + PostgreSQL on a separate VM with agents on each host. When the number of hosts exceeds 20 or locations are distributed, add Zabbix Proxy in each zone. The proxy buffers data and sends it in batches—reducing server load and tolerating network interruptions.

Minimum requirements for a server with 10 hosts: 2 vCPU, 4 GB RAM, 50 GB SSD (history retention 90 days). For individual consultation, contact us—we will select the optimal scheme for your project.

Installing Zabbix Server in 5 Steps

1. Add the Zabbix 7.0 repository and install packages: server, frontend, agent2.
2. Create a PostgreSQL user and database for Zabbix.
3. Import the database schema.
4. Configure the server settings.
5. Start the server and enable autostart.

wget https://repo.zabbix.com/zabbix/7.0/ubuntu/pool/main/z/zabbix-release/zabbix-release_7.0-2+ubuntu22.04_all.deb
dpkg -i zabbix-release_7.0-2+ubuntu22.04_all.deb
apt update && apt install -y zabbix-server-pgsql zabbix-frontend-php zabbix-sql-scripts zabbix-agent2
sudo -u postgres createuser --pwprompt zabbix
sudo -u postgres createdb -O zabbix zabbix
zcat /usr/share/zabbix-sql-scripts/postgresql/server.sql.gz | sudo -u zabbix psql zabbix

Configuration /etc/zabbix/zabbix_server.conf:

DBHost=localhost
DBName=zabbix
DBUser=zabbix
DBPassword=your_password
StartPollers=10
StartPingers=5
CacheSize=128M
HistoryCacheSize=64M
ValueCacheSize=256M

Installing Zabbix Agent on the target host:

apt install -y zabbix-agent2
cat > /etc/zabbix/zabbix_agent2.conf << EOF
Server=<ZABBIX_SERVER_IP>
ServerActive=<ZABBIX_SERVER_IP>
Hostname=web-server-01
AllowKey=system.run[*]
EOF
systemctl enable --now zabbix-agent2

Why Custom Templates Are Better Than Pre-built Ones

Pre-built templates include hundreds of metrics, most of which are unnecessary. We disable uninformative triggers and add business metrics: API response time, active session count, log errors. On one project, we disabled 80% of default triggers—false alarms dropped from 50 to 2 per day.

Example of setting a user parameter for PHP-FPM:

UserParameter=php-fpm.status[*],curl -s --unix-socket /run/php/php8.2-fpm.sock http://localhost/status?json

Triggers that don't generate noise:

Optimizing Data Storage with TimescaleDB

When handling large volumes of metrics, PostgreSQL may slow down. The solution is TimescaleDB. Migrate the existing database and enable compression:

SELECT create_hypertable('history', 'clock', chunk_time_interval => 86400, migrate_data => true);
SELECT create_hypertable('history_uint', 'clock', chunk_time_interval => 86400, migrate_data => true);
ALTER TABLE history SET (timescaledb.compress, timescaledb.compress_segmentby = 'itemid');
SELECT add_compression_policy('history', INTERVAL '7 days');

TimescaleDB compresses data 10 times more efficiently than standard PostgreSQL—reducing disk load and speeding up queries. We set Housekeeping: store trends for 365 days, history for 90 days. After enabling compression, disk usage drops by 90%, and query speed for the last day increases 5–10 times.

What's Included in the Work

• Deployment of Zabbix Server + PostgreSQL
• Installation and configuration of agents on all servers
• Integration of pre-built templates and development of custom ones
• Setup of triggers and actions (Telegram, email)
• Creation of web scenarios for URL monitoring
• Dashboard construction (Zabbix + Grafana if needed)
• Storage optimization (TimescaleDB, housekeeping)
• Documentation and administrator training

Our Experience and Guarantees

Over 6 years, we have deployed monitoring for 50+ web projects—from small e-commerce sites to high-load services with 500+ hosts. Our engineers are Zabbix certified and experienced with cluster configurations. We guarantee that after setup, you will receive only meaningful alerts, and the dashboard will reflect the real system state.

Timeline and Cost

Basic installation with monitoring for 3–5 servers takes 1 business day. Full setup with custom elements and dashboards takes 3–5 days. Migration from another system adds 1–2 days. The cost is calculated individually—contact us for an evaluation of your project. Typical savings range from $5,000 to $50,000. Basic setup starts at $1,000.

Get a consultation—write to us, and we will offer the optimal solution for your budget and timeline.

Setup Web Analytics: GA4, GTM, Yandex.Metrica, and Amplitude

We often see: conversion rate 1.2%, traffic grows, but conversion stays flat. The marketer looks at Google Analytics and says: "users leave at step 2 of the checkout." The developer opens the same step — no errors, Sentry is silent. So it's not a JS bug, but a UX issue or skewed data from analytics. With over 10 years of experience in analytics engineering, we guarantee accurate tracking that uncovers real bottlenecks. Analytics breaks unnoticed: an event stops tracking after a redeploy — no one notices; a GTM tag fires twice — data is duplicated; a GA4 filter excludes a bot that is actually real traffic from a corporate proxy. An audit of your current tags will find the cause within a week.

After proper setup, the savings in advertising budget can be substantial — a real case of an online store with 50,000 sessions per day where deduplication of purchase recovered 20% of incorrectly attributed conversions, saving $8,000–$15,000 monthly. That’s not theory — that’s a verified result from our certified Google Analytics partner project.

Why do GA4 events duplicate and how to fix it?

Universal Analytics is gone, replaced by GA4's event-based model. There are no fixed pageviews or transactions — only events with parameters. This is more flexible but requires proper event design. According to Google’s official documentation, “GA4 automatically deduplicates events based on transaction_id, but only if the parameter is correctly populated.” Many implementations miss this.

Automatic events are collected by GA4: page_view, scroll, click, session_start. Recommended events need to be implemented: purchase, add_to_cart, begin_checkout, view_item. Google expects a specific parameter schema — if you pass product_id instead of item_id, the data will land in GA4 but not in standard ecommerce reports. Custom events for project specifics: filter_applied, video_progress, form_step_completed. Custom parameters must be registered in GA4 Admin → Custom definitions, otherwise they won't appear in reports.

A common mistake is the purchase event being duplicated. Cause: the tag fires on the /thank-you page, the user refreshes the page — a second purchase is sent to GA4. Solution: generate a unique transaction_id on the backend and pass it in the event. In our experience, 80% of e-commerce stores have this issue. GA4 deduplicates based on it (in theory — verify with DebugView). Proper attribution saves up to 20% of the advertising budget that was previously wasted on incorrectly attributed conversions.

How to set up the data layer to avoid data loss?

GTM is a tool for managing tags without code deployment. But "no code" doesn't mean "no architecture." The data layer is the foundation. We pass data from the application to GTM via dataLayer.push(). Structure: event + contextual data. For e-commerce: before opening a product page — push with product data. GTM tag reads from the data layer, not from the DOM.

window.dataLayer = window.dataLayer || [];
dataLayer.push({
  event: 'view_item',
  ecommerce: {
    items: [{
      item_id: 'SKU-12345',
      item_name: 'Product name',
      price: 1990.00,
      currency: 'USD'
    }]
  }
});

Bad practice: GTM tag parses the DOM — looks for the price in span.price, the name in h1. This breaks with any layout change. Good practice: always use the data layer. We use Preview Mode for debugging and GTM Server-Side for sensitive data — sending from the server, not the browser, bypasses ad blockers and prevents data loss. A properly implemented data layer reduces tracking errors by 95%.

How does Yandex.Metrica complement web analytics?

For a Russian audience, Metrica is a must — especially Webvisor. Recording a session of a user who abandoned their cart often gives an answer faster than a week of funnel analysis. Goals in Metrica: event-based (via ym(COUNTER_ID, 'reachGoal', 'GOAL_NAME')) or automatic (button click, page visit). Integration with CRM via Metrica Plus — passing offline conversions. Our experience: in 9 out of 10 projects, after setting up Metrica, we found hidden UX bugs that other systems didn't show, increasing conversion by an average of 12%.

What does product analytics give in Amplitude?

Amplitude is a product tool, unlike marketing-oriented GA4 and Metrica. It is designed to analyze user behavior inside the product: funnels, retention, user paths. Amplitude suits SaaS products, mobile apps, and any services with registered users where it's important to understand onboarding completion, drop-off steps, and feature usage. Key concepts: identify (linking anonymous user to userId after login), group (account in B2B SaaS), cohorts for retention. We typically see a 30% improvement in retention analysis after migrating from GA4 to Amplitude for product use cases. Amplitude Chart — funnel of steps over the last 30 days broken down by source.

Monitoring Data Quality

Analytics without monitoring is a black box. We set up:

• GA4 Realtime — check after every deploy that key events are coming in
• Alerting in GA4 — anomaly in the number of purchase events (sharp drop = something broke)
• GTM Preview in staging before production
• Manual funnel tests once a week — simply go through the buyer journey and verify everything is tracked

What the work includes

Process and timeline

1. Audit of existing tags and data (2 days)
2. Event schema design (2 days)
3. Data layer development and tag setup (3–5 days)
4. QA in Preview Mode and staging (2 days)
5. Deploy and dashboard setup (1 day)

Cost is calculated individually. Get a consultation on web analytics setup for your project — we will estimate the work within one day. Contact us to get started with a free audit of your current tracking.