tutorial

Monitoring Coralogix with Vigilmon: Real-Time Observability Platform Health Checks

How to monitor Coralogix with Vigilmon — HTTP health checks on the Coralogix ingestion endpoint, dashboard availability, SSL certificate monitoring, and alerting for your log and metrics observability infrastructure.

Coralogix is the real-time observability platform using Streama technology that analyzes logs, metrics, and traces in-stream without indexing — offering machine learning-based anomaly detection, log pattern analysis, and Loggregation to dramatically reduce storage costs versus traditional SIEM and log platforms. When Coralogix's ingestion endpoint goes down, your logs, metrics, and traces stop reaching the platform silently — Fluentd, Logstash, and OpenTelemetry Collector pipelines begin buffering or dropping data depending on their backpressure configuration. When the Coralogix dashboard becomes unreachable, your team loses access to real-time log analysis, alert management, and anomaly detection dashboards exactly when they are needed most during incidents. Vigilmon gives you external uptime monitoring for Coralogix — ingestion endpoint availability, dashboard health, SSL certificate validity, and alerting before your observability backbone fails.

What You'll Build

  • An HTTP monitor on Coralogix's log ingestion endpoint to detect data pipeline failures
  • A monitor on the Coralogix dashboard to catch web application outages
  • An SSL certificate monitor for your Coralogix domain
  • Alerting rules that notify your team when log ingestion stops working

Prerequisites

  • An active Coralogix account with API access — Coralogix is a managed SaaS platform with regional endpoints
  • Your Coralogix regional endpoint URL (varies by region: EU, US, India, Singapore, Australia)
  • A free account at vigilmon.online

Step 1: Understand Coralogix's Regional Architecture

Coralogix operates regional data residency clusters. Your ingestion endpoint and dashboard URL depend on the region where your Coralogix account was created:

| Region | Ingestion endpoint | Dashboard | |---|---|---| | EU West (Ireland) | https://ingress.coralogix.com | https://dashboard.eu2.coralogix.com | | US East (Ohio) | https://ingress.coralogixsg.com | https://dashboard.cx498.coralogix.com | | India (Mumbai) | https://ingress.coralogix.in | https://dashboard.app.coralogix.in | | Singapore | https://ingress.coralogixsg.com | https://dashboard.coralogixsg.com | | Australia | https://ingress.coralogix.com.au | https://dashboard.coralogix.com.au |

Use the endpoint matching your account's region. Monitor the ingestion endpoint your log shippers are configured to use — this is the URL in your Fluentd, Logstash, or OpenTelemetry Collector configuration.

Step 2: Monitor the Coralogix Ingestion Endpoint

The ingestion endpoint is the most critical component — it receives all logs, metrics, and traces from your infrastructure via the Coralogix Logs API, OpenTelemetry exporter, or Fluentd/Logstash plugins. A liveness check on the ingestion endpoint confirms the intake service is accepting connections:

curl -I https://ingress.coralogix.com/logs/v1/singles
# A 200, 401, or 405 confirms the endpoint is alive
  1. Log in to Vigilmon → Add Monitor → HTTP.
  2. URL: Your regional Coralogix ingestion endpoint (e.g., https://ingress.coralogix.com/logs/v1/singles).
  3. Check interval: 60 seconds.
  4. Response timeout: 15 seconds.
  5. Expected status: 200 or 401 (unauthenticated GET returns 401 — set to match the actual response from your regional endpoint).
  6. Label: Coralogix log ingestion endpoint.
  7. Click Save.

This monitor catches:

  • Regional Coralogix service degradation or outages
  • TLS/certificate issues preventing shipper connections
  • DNS resolution failures for the ingestion endpoint
  • Network path failures between your infrastructure and Coralogix's regional data center

Alert sensitivity: Set to trigger after 1 consecutive failure. A single ingestion outage means every log shipper in your infrastructure is no longer delivering data — your Coralogix dashboards go stale immediately.

Step 3: Monitor the Coralogix Dashboard

The Coralogix dashboard provides real-time log search, Loggregation views, anomaly detection alerts, and metrics visualization. An HTTP check on the dashboard confirms the web application is serving requests:

curl -I https://dashboard.eu2.coralogix.com
# Returns 200 with text/html content
  1. Add Monitor → HTTP.
  2. URL: Your regional Coralogix dashboard URL (e.g., https://dashboard.eu2.coralogix.com).
  3. Check interval: 60 seconds.
  4. Response timeout: 15 seconds.
  5. Expected status: 200.
  6. Keyword: Coralogix (appears in the page title).
  7. Label: Coralogix dashboard.
  8. Click Save.

Incident correlation note: If your Coralogix dashboard is unavailable during a production incident, your team loses access to the real-time log analysis needed to investigate. Monitor the dashboard independently from the ingestion endpoint — the two can degrade separately during partial regional failures.

Step 4: Monitor the OpenTelemetry OTLP Endpoint

Coralogix accepts OpenTelemetry Protocol (OTLP) telemetry at a dedicated endpoint. If your services ship traces or metrics via OpenTelemetry Collector, the OTLP endpoint is a separate ingestion path that warrants independent monitoring:

curl -I https://ingress.coralogix.com/v1/traces
# Returns 200 or 405 for a GET request on the OTLP trace endpoint
  1. Add Monitor → HTTP.
  2. URL: https://ingress.coralogix.com/v1/traces (adjust for your region and OTLP path).
  3. Check interval: 2 minutes.
  4. Response timeout: 10 seconds.
  5. Expected status: 200 or 405.
  6. Label: Coralogix OTLP traces endpoint.
  7. Click Save.

Why monitor OTLP separately: Coralogix's log ingestion API and OTLP endpoints run independently. A misconfiguration or temporary issue on the OTLP side can stop all trace and metric ingestion while log shipping continues normally — a single monitor on the log endpoint would miss this split failure.

Step 5: Monitor SSL Certificates

Coralogix uses TLS for all ingestion endpoints. An expired or misissued certificate causes OpenTelemetry Collector, Fluentd, and Logstash to raise TLS errors, stopping data delivery across your entire log pipeline:

openssl s_client -connect ingress.coralogix.com:443 2>/dev/null | openssl x509 -noout -dates
  1. Add Monitor → SSL Certificate.
  2. Domain: ingress.coralogix.com (use your regional ingestion hostname).
  3. Alert when expiry is within: 30 days.
  4. Alert again: 14 days, 7 days, 3 days, 1 day.
  5. Click Save.

Why SSL monitoring matters for Coralogix: Unlike SaaS platforms where users manually notice a browser warning, log shippers running as unattended daemons will silently fail TLS verification after a certificate change and stop delivering data. You may not notice the gap in Coralogix for hours if there is no external availability check.

Step 6: Configure Alerting

In Vigilmon under Settings → Notifications, configure your alert channels:

| Monitor | Trigger | Action | |---|---|---| | Log ingestion endpoint | Non-200/401 response or timeout | Check Coralogix regional status page; review log shipper buffer depth; verify DNS resolution | | Dashboard | Non-200 or keyword missing | Check Coralogix status page; verify regional web service; use status.coralogix.com | | OTLP traces endpoint | Unexpected status | OpenTelemetry Collector losing connection; check collector logs for TLS or connection errors | | SSL certificate | < 30 days to expiry | Coralogix-managed certificates auto-renew, but verify; check for unexpected certificate changes |

Alert after: 1 consecutive failure for the log ingestion endpoint. 2 consecutive failures for dashboard and OTLP monitors.

Common Coralogix Failure Modes and What Vigilmon Catches

| Scenario | Vigilmon monitor | |---|---| | Regional Coralogix outage | Ingestion and dashboard monitors fire; check status.coralogix.com | | TLS certificate change causes shipper rejection | SSL monitor fires at 30-day threshold; shippers raise TLS errors | | DNS resolution failure for ingestion endpoint | Ingestion monitor fires; all shippers stop delivering | | OTLP endpoint degraded (logs still healthy) | OTLP monitor fires; traces stop while logs continue | | Dashboard incident during production outage | Dashboard monitor fires; team cannot access real-time log analysis | | Rate limit exceeded causing HTTP 429 responses | Ingestion monitor fires; Coralogix dropping data under traffic spike | | Network path failure to regional data center | All regional monitors fire; all telemetry delivery stops | | Coralogix API key rotation causing 401s | Ingestion returns 401; update shipper configurations | | Partial regional degradation (ingestion healthy, queries slow) | Dashboard monitor may fire; investigate via Coralogix status page | | Firewall rule blocking Coralogix egress port 443 | All monitors fire; immediate investigation path for network team |

Monitoring Data Flow vs. Service Availability

Vigilmon monitors whether Coralogix's endpoints are reachable from external probes — it does not verify that your log shippers are successfully delivering data end-to-end. For deeper pipeline monitoring:

  • Shipper queue depth: Fluentd, Logstash, and Fluent Bit expose internal buffer metrics. A growing buffer combined with a healthy Coralogix ingestion monitor indicates a shipper configuration issue, not a Coralogix outage.
  • Log volume baselines: Coralogix's dashboard shows ingestion volume over time. A sudden drop in ingested log volume when the ingestion endpoint is healthy suggests shippers have stopped running or been misconfigured on the source hosts.
  • Loggregation drift: If Coralogix's Loggregation patterns shift unexpectedly, it may indicate a change in log format from application deployments rather than a platform issue.

Vigilmon catches infrastructure-level failures — endpoint unreachability, certificate expiry, regional outages. End-to-end log delivery verification requires shipper-side metrics alongside external uptime monitoring.

Coralogix analyzes your logs, metrics, and traces in real-time without indexing overhead, but your observability platform itself needs monitoring. A Coralogix ingestion outage silently stops all log delivery from every shipper in your infrastructure — your dashboards go stale exactly when you need them most during incidents. Vigilmon checks Coralogix's ingestion endpoint, dashboard, OTLP traces path, and SSL certificate on a 60-second cycle, so you know within a minute when your observability backbone stops receiving data.

Start monitoring Coralogix in under 5 minutes — register free at vigilmon.online.

Monitor your app with Vigilmon

Free plan — 5 monitors, no credit card required. Up and running in 60 seconds.

Start free →
← Back to all articles