Log monitoring
Docker va service loglarini kuzatish, sahifalash, real-time oqim va muhim xatolar bo'yicha alert yuborish.
Docker Alerting dashboardi har bir mijozning o'z serverida ishlaydi. Yengil agentlar esa monitoring qilinadigan server, VM, container yoki Kubernetes klasterlariga o'rnatilib, loglar, metrikalar va status voqealarini shu dashboardga yuboradi.
Platforma dashboardga kirish sahifasi emas, balki mijoz o'z infratuzilmasida ishga tushiradigan monitoring mahsulotidir.
Docker va service loglarini kuzatish, sahifalash, real-time oqim va muhim xatolar bo'yicha alert yuborish.
Container o'chishi, restart bo'lishi, crash yoki unhealthy holatlari aniqlanganda alohida notification yuboriladi.
Har bir server yoki klasterga agent o'rnatiladi. Dashboardda kerakli server tanlanib, shu node ma'lumotlari ko'riladi.
CPU va RAM bosimini, top processlarni, Docker resource usage ni va aynan qaysi jarayon resurs yeyayotganini ko'rsatadi.
Log alert va status alert sozlamalari alohida yuradi. Chat ID, topic ID, interval va guruh havolasi UI orqali beriladi.
Admin va oddiy user rollari bilan kirish nazorati, sessiya muddati, xavfsiz cookie va rolga qarab imkoniyatlar.
Docker Compose, Docker Swarm, GitLab CI/CD va kelgusida Kubernetes muhitlariga mos joylashtirish modeli.
Home Page faqat mahsulotni tanishtiradi. Operatsion dashboard har bir mijozning serveri, private cloudi yoki ichki tarmog'ida joylashadi.
Avval mijoz o'z dashboardini ko'taradi, keyin monitoring qilinadigan serverlarga agentlar ulanadi.
Mijoz serverida Docker Compose yoki Swarm orqali dashboard ishga tushiriladi.
docker stack deploy -c docker-compose.yml dashboard
Dashboard settings ichidan har bir agent uchun token yaratiladi va server nomi belgilanadi.
AGENT_TOKEN=generated-token
Monitoring qilinadigan host, VM, container host yoki Kubernetes nodega agent o'rnatiladi.
docker compose up -d agent
Log va status alertlari uchun alohida chat, topic, interval va notification qoidalari beriladi.
log alerts != status alerts
Dashboard mijoz serverida `dashboard` stack nomi bilan ko'tariladi. Agent esa monitoring qilinadigan alohida serverga o'rnatilib, dashboard endpointiga report yuboradi.
Postgres bazasi, gateway, log dashboard, status dashboard va worker servicelar bir stack ichida yuradi.
services:
postgres:
image: postgres:16.13-alpine
environment:
POSTGRES_DB: docker_alerting
POSTGRES_USER: docker_alerting
POSTGRES_PASSWORD_FILE: /run/secrets/postgres_password
secrets:
- postgres_password
volumes:
- dashboard-postgres-data:/var/lib/postgresql/data
dashboard:
image: xondev/docker_alerting:dashboard
command: ["python3", "-u", "docker_log_alert.py", "gateway"]
environment:
DB_HOST: postgres
DB_NAME: docker_alerting
DB_USER: docker_alerting
DB_PASSWORD_FILE: /run/secrets/postgres_password
FRONTEND_URL: https://xondev.uz
BACKEND_URL: https://xondev.uz
CORS_ALLOWED_ORIGINS: https://xondev.uz,https://log.xondev.uz
COOKIE_SECURE: "true"
ports:
- "18082:18082"
secrets:
- postgres_password
- google_client_id
- google_client_secret
secrets:
postgres_password:
external: true
name: docker_alerting_postgres_password
google_client_id:
external: true
name: docker_alerting_google_client_id
google_client_secret:
external: true
name: docker_alerting_google_client_secret
volumes:
dashboard-postgres-data:
docker stack deploy -c docker-compose.dashboard.demo.yml dashboard
Har bir kuzatiladigan server, VM yoki Docker hostga alohida agent qo'yiladi.
services:
docker-alerting-agent:
image: xondev/docker_alerting:agent
restart: unless-stopped
command:
- python3
- -u
- docker_log_alert.py
- agent
- --server-url
- https://log.xondev.uz
- --agent-token
- CHANGE_ME_AGENT_TOKEN
- --node-name
- CHANGE_ME_NODE_NAME
- --interval
- "60"
volumes:
- /var/lib/docker/containers:/var/lib/docker/containers:ro
- /var/run/docker.sock:/var/run/docker.sock:ro
network_mode: host
docker compose -f docker-compose.agent.demo.yml up -d
Mahsulot kichik Docker hostdan enterprise muhitigacha o'sib boradigan monitoring ehtiyojlariga moslanadi.
Bir nechta serverdagi containerlar, restartlar va xatolarni alohida monitoring steki qurmasdan kuzatish.
Har bir mijozga alohida dashboard o'rnatib, agentlarni shu mijozning o'z serverlariga ulash.
Billing, API, queue, worker va database atrofidagi service statusini tez ko'rish va jamoaga xabar berish.
Log alert, status alert va interval qoidalari bilan takroriy notification shovqinini boshqarish.
Docker hostlardan Kubernetes klasterlarga o'tishda agentli monitoring modelini saqlab qolish.
SSO, RBAC, multi-tenant va SLA talablari bo'lgan yopiq tarmoqdagi korporativ muhitlar.
Har bir tarifda agent limiti, log retention, alert kanallari va team imkoniyatlari aniq farq qiladi.
Kichik loyihalar va birinchi integratsiya uchun.
Startaplar va kichik biznes uchun.
O'rta hajmdagi kompaniyalar va production jamoalar uchun.
Katta korxonalar va Enterprise mijozlar uchun.
| Capability | Free | Go | Plus | Pro |
|---|---|---|---|---|
| Agent limiti | 2 | 10 | 50 | Custom/Unlimited |
| Retention | 24 soat | 7 kun | 30 kun | 90+ kun |
| Alert kanallari | 1 Telegram | Telegram + Email | Escalation | Custom integrations |
| Access control | 1 admin | Admin/user | Team management | SSO/RBAC/Multi-tenant |
Platformaning ishlash modeli dashboard, agent va alert oqimlari atrofida qurilgan.
Dashboard mijozning o'z serverida, private cloudida yoki Docker Swarm muhitida ishlaydi. Home Page operatsion panel emas, faqat mahsulot taqdimoti.
Agentlar loglar, container statusi, restart/crash voqealari, service health va monitoring payloadlarini mijoz dashboardiga yuboradi.
Self-hosted modelda ma'lumotlar mijoz infratuzilmasida qoladi. Agentlar mijozning o'z dashboard endpointiga ulanadi.
Ha. Log alert va container status alert sozlamalari alohida bo'ladi, shuning uchun turli guruh, topic va interval ishlatish mumkin.
Arxitektura agentli bo'lgani uchun Docker host, VM va Kubernetes klasterlar bilan ishlashga moslanadi. Enterprise integratsiyada maxsus adapterlar qo'shiladi.
Ha. Agentlar soni, jamoa hajmi, alert kanallari va enterprise talablar oshganda tarifni Go, Plus yoki Pro ga ko'tarish mumkin.
User email-parol yoki Google account bilan databasega saqlanadi. Keyingi safar shu account bilan login bo'ladi va protected portal orqali client paketlarni ko'radi.