LogDNA (Mezmo) Operations

Service: LogDNA / Mezmo log management SaaS Element type: SaaS (external) Host: bms-1 (ns367522, 94.23.26.113) Status: Active — paid subscription


Overview

LogDNA (rebranded as Mezmo) provides short-term log aggregation and search for Pinbox24 production containers running on bms-1. It is the primary tool for ad-hoc log search and debugging on the production app server.


Agent

FieldValue
Servicelogdna-agent (systemd)
Hostbms-1 (94.23.26.113)
Config file/etc/logdna.conf
API key location/etc/logdna.conf — field key
Managed byroot on bms-1

Check agent status:

ssh root@94.23.26.113 "systemctl status logdna-agent"

Restart agent:

ssh root@94.23.26.113 "systemctl restart logdna-agent"

View agent logs:

ssh root@94.23.26.113 "journalctl -u logdna-agent --since '1 hour ago'"

Shipped log sources

The agent is configured to ship logs from these Pinbox24 app containers on bms-1:

Tag / sourceContainer / app
v42-prodPinbox24 v42 production
v42-notify-prodPinbox24 v42 notification service
s3-v2-v42-prodS3 / storage service for v42

Additional containers may be included via Docker label discovery — check /etc/logdna.conf for the full tags / exclude config.


Log retention

Retention is determined by the active LogDNA/Mezmo plan. Historically this is a few days of hot storage. Logs are not archived to Wasabi — LogDNA is for short-term debug only. Long-term log storage is via Promtail → Loki on vps-i1.


Access


Key rotation

  1. Generate a new ingestion key in the Mezmo dashboard → Settings → API Keys.
  2. On bms-1: echo "key = <new-key>" | sudo tee /etc/logdna.conf (preserve other config lines).
  3. Restart the agent: systemctl restart logdna-agent.
  4. Verify logs appear in the Mezmo dashboard within 2 minutes.
  5. Revoke the old key in the Mezmo dashboard.
  6. Update compliance_notes in dev_r_services row logdna.

Compliance checklist

CheckStatusNotes
Workbook existsyesThis document
Monitoring enabledn/aSaaS — no exporter; agent health via systemctl
Backupn/aShort-term log buffer, not a data source to back up
Key rotation proceduredefinedSee section above
Health checkmanualsystemctl status logdna-agent on bms-1