LogDNA rebranded to Mezmo in 2022, but the tool most developers know it as remains the same: a clean, fast log aggregation platform built for teams that are drowning in log output and need a better way to search, filter, and alert on it. Whether you call it LogDNA or Mezmo, it occupies a specific position in the observability stack — and that position has a notable gap.
This article explains what LogDNA/Mezmo does, what it doesn't do, and why external uptime monitoring is the complementary layer it can't replace.
What LogDNA (Mezmo) Is
LogDNA, now operating as Mezmo, is a log management and analysis platform. It aggregates log streams from your infrastructure and applications, indexes them for fast search, and provides alerting on log patterns and anomalies.
Core capabilities include:
- Log aggregation: Collect logs from servers, containers, Kubernetes pods, serverless functions, and cloud provider services via lightweight agents or direct API shipping
- Log search: Full-text and field-based search across log streams with sub-second response times
- Log archiving: Long-term retention and export to S3, IBM Cloud Object Storage, or similar
- Alerting: Trigger alerts on log patterns — specific strings, regex matches, field threshold values
- Parsing: Automatic and custom parsing of structured (JSON) and semi-structured log formats
- Live tail: Real-time streaming log view for active debugging sessions
- IBM Cloud integration: Deep integration as the default logging service for IBM Cloud workloads
LogDNA's original differentiation was simplicity and speed. Competing platforms like Splunk required significant operational overhead; LogDNA offered a fast path to centralised log access with minimal configuration. The agent (logdna-agent) is a single process that tails log files or receives syslog output and ships to the platform.
The Mezmo rebrand added a "telemetry pipeline" concept — routing and transforming log data between sources and destinations — which positions it as a data routing layer in addition to a log viewer.
What Vigilmon Is
Vigilmon is an external uptime monitoring platform. It runs checks against your HTTP endpoints, TCP ports, and SSL certificates from multiple geographic probe locations on a continuous schedule. When a confirmed outage is detected — via multi-region consensus, not single-probe alerting — it notifies via Slack, email, or webhook.
Key characteristics:
- Outside-in monitoring: Probes run on Vigilmon's infrastructure, checking your public endpoints exactly as a user would
- Multi-region consensus: An alert only fires when multiple independent regional probes agree on a failure — eliminating false positives from transient regional blips
- SSL certificate monitoring: Tracks expiry dates, alerts before certificates expire
- Built-in status page: Auto-updating, customer-facing, no separate product required
- Zero-instrumentation: No agent to install, no SDK to integrate, no config to manage on your infrastructure
Setup: add your URL, verify the check, done. Under two minutes.
What Log Monitoring Misses
The core architectural limitation of log-based monitoring is that it only sees what your application generates. If a request reaches your application, it produces a log line. If it doesn't reach your application — because of a DNS failure, a CDN misconfiguration, a network routing issue, an expired certificate — your application logs are silent.
This creates a category of failures that log monitoring cannot detect:
DNS failures: Your application is running. DNS resolution for your domain is broken. Users get "server not found." Your logs: nothing unusual — zero incoming requests.
SSL certificate expiry: Your certificate expired. Browsers refuse to load your site. Your application: still running, happy to serve requests that never arrive.
CDN edge failure: Your CDN misconfigures your domain's routing. Traffic hits the CDN edge and returns errors before reaching your origin. Your application: no errors visible in logs.
Regional routing failure: A BGP route gets dropped between two network providers. Users in one geography lose access to your site. Your application: no signal — traffic from that region simply stops arriving.
Third-party DNS provider outage: Your DNS provider has downtime. Your domain becomes unreachable. Your application: unaware, serving zero requests.
In every one of these scenarios, an internal log monitoring tool gives you a clean dashboard right up until your CTO texts you to say the site is down and customers are tweeting about it.
External monitoring catches all of them, because external monitoring checks whether your URL is reachable from the public internet — which is exactly what your users experience.
Complementary, Not Competing
The useful framing: LogDNA/Mezmo and Vigilmon solve adjacent problems in the same domain.
| Layer | Tool | What it answers | |---|---|---| | Internal observability | LogDNA / Mezmo | Why are errors happening? What do my logs say? | | External availability | Vigilmon | Is my service reachable from the internet? |
These aren't substitutes. A team running both gets complete coverage: internal signals for debugging, external signals for confirming customer-facing availability.
A team running only LogDNA/Mezmo knows a great deal about the internal state of their application — and has a blind spot exactly where their users experience problems.
Pricing Comparison
LogDNA / Mezmo Pricing
LogDNA/Mezmo pricing is volume-based, with tiers determined by log ingestion:
| Tier | Approximate Cost | Data Retention | |---|---|---| | Community (Free) | $0 | Up to 50 MB/day, 7-day retention | | Log Analysis | ~$1.50–3.00/GB ingested | 7–30 day retention | | Enterprise | Custom contract | Extended retention, dedicated support |
Practical costs:
A production application logging at 5 GB/day would ship ~150 GB/month, costing approximately $225–450/month at standard rates. High-throughput services can push well above this.
The free tier (50 MB/day) covers very small applications or development environments, not production workloads at scale.
Vigilmon Pricing
| Tier | Cost | What's Included | |---|---|---| | Free | $0 | 5 monitors, 1-minute intervals, status page, Slack alerts | | Pro | ~$10–20/month | More monitors, 30-second check intervals | | Self-hosted | ~$5/month (VPS only) | Unlimited monitors, open source |
External uptime monitoring doesn't scale with data volume — it's a fixed number of endpoints checked on a schedule. Vigilmon's free tier covers five endpoints indefinitely, with no per-request or per-GB costs.
Feature Comparison
| Feature | Vigilmon | LogDNA / Mezmo | |---|---|---| | External uptime monitoring | Yes — core product | No | | Multi-region consensus alerting | Yes | No | | HTTP/HTTPS monitoring | Yes | No | | TCP port monitoring | Yes | No | | SSL certificate monitoring | Yes | No | | Customer-facing status page | Yes, built in | No | | Log ingestion and search | No | Yes — core product | | Log-based alerting | No | Yes | | Live log tailing | No | Yes | | Log archiving | No | Yes | | Kubernetes log collection | No | Yes | | Agent required | No | Yes (logdna-agent) | | Pricing model | Flat rate | Per GB ingested | | Free tier | 5 monitors, permanent | 50 MB/day | | Self-hostable | Yes (open source) | No |
Who Should Use LogDNA / Mezmo
Choose LogDNA / Mezmo if:
- You need centralised log access across services. If your team is SSH-ing into individual servers to run
tail -f, centralised log aggregation is a significant quality-of-life improvement. - Debugging requires searching recent logs. Full-text search across aggregated logs from multiple services is LogDNA's core strength.
- You're on IBM Cloud. LogDNA is IBM Cloud's native log management service with first-party integration.
- You want log-based alerting. Alerts triggered by log patterns ("ERROR" rate above threshold, specific exception strings appearing) require a log platform.
- Your team does post-incident analysis. Log retention with timeline reconstruction is essential for understanding root cause after an incident.
Who Should Use Vigilmon
Choose Vigilmon if:
- You need to know the moment your site goes down from users' perspective. This is the question that log monitoring structurally cannot answer.
- You want to eliminate false-positive alerts. Multi-region consensus means you only get paged when something is genuinely down — not when a single probe has a transient failure.
- SSL certificate monitoring is on your list. Certificate expiry is a common cause of outages. Vigilmon monitors expiry dates and alerts before they become production problems.
- You need a status page. LogDNA/Mezmo doesn't have one. Vigilmon's is included and auto-updating.
- Zero ops overhead matters. No agent to install, update, or monitor. No log shipper to configure. No storage costs.
Running Both: The Practical Setup
For most teams, the recommendation is to run both — the costs don't prohibit it.
LogDNA/Mezmo handles your internal observability story: search for errors, correlate log events, set up log-based alerts for specific exception patterns, keep a searchable record for post-incident review.
Vigilmon handles your external availability story: confirm the site is up, catch SSL expiry, alert on regional access failures, give your users a status page.
When an incident happens, you want both: Vigilmon tells you something is broken and from where, LogDNA/Mezmo helps you understand why.
Adding Vigilmon's free tier to an existing LogDNA/Mezmo setup closes the external monitoring gap at zero additional cost. Five endpoints, 1-minute check intervals, multi-region consensus alerting, status page included.
Conclusion
LogDNA/Mezmo is a competent log management platform with a clean interface, fast search, and straightforward log aggregation. If your team needs centralised log access and log-based alerting, it's a reasonable choice.
But log management is an inside-out tool: it only sees what your application produces internally. External availability — whether your users can reach your application, whether your DNS resolves, whether your SSL certificate is valid — is a gap that log monitoring leaves open.
Vigilmon closes that gap. The two tools are designed for adjacent problems, and running both gives you the complete picture that either alone cannot provide.
Start external monitoring free at vigilmon.online — 5 monitors, multi-region consensus, status page, Slack alerts, no credit card.
Tags: #monitoring #devops #logdna #mezmo #uptime #logging #observability