Skip to main content
The Mezmo Agent reads log files from the host where it is installed, and uploads the log data to Mezmo via a secure HTTPS connection, where it is parsed and processed according to the parameters set in the Mezmo Agent configuration file. The Mezmo Agent runs on Kubernetes, Openshift, Linux, and Windows. The Mezmo Agent is written in Rust, and uses the Linux kernel to monitor the log files and directories for changes, rather than having to poll these files constantly. This implementation frees up CPU utilization and improves stability.
As of 5/1/2025, versions below 3.8 will be deprecated. Deprecated agents should continue to work, but Mezmo will only debug issues with ingestion on supported versions.

​
GitHub Repository

For complete information about installing and configuring the Mezmo Agent, check out the source code and documentation in our GitHub repository. https://github.com/logdna/logdna-agent-v2

​
Default Configuration File

You can find the default configuration yaml file in the Agent directory at /etc/logdna/config.yaml. You can find more information in the Configuration section of the GitHub documentation.

​
Agent 1.x-2.x (Deprecated)

GitHub Repository For complete information about installing and configuring the older Mezmo Agent, check out the source code and documentation in our GitHub repository. https://github.com/logdna/logdna-agent
The certificates in versions <2.2.1 have expired, and it is not possible to update the certificate model used in these versions. Mezmo recommends that you to use latest version of version 2, or agent versions above 2.2 on version 1. You can find more information in this blog post.
Starting from version 3.6 GA, we recommend upgrading to version 3.x, which is a more performant Agent that can handle all the types of logs supported by Version 1.

​
Mezmo Agent FAQS

​
How do I tell the Mezmo Agent what to log?

By default, the Mezmo Agent automatically logs all .log and extensionless files located under /var/log/, but if you want to log other directories or files, you can use these commands in a host terminal to specify additional directories or files: For directories:
For files:
If you need more complex logic, you can also view and set specific logging paths, as well as use glob patterns by editing /etc/LogDNA.conf or /etc/LogDNA.env`, depending on the agent version.

​
Is the Mezmo Agent open source?

Yes! You can view, and contribute to, the source code on GitHub for both Agentv1 and Agent v2, and even build the agent yourself. We also love the open source community, so please feel welcome to submit PRs or report any issues you find. Check out our contributing guide for more info.

​
How do I use host tags?

Host tags let you automatically group hosts into dynamic host groups without having to explicitly assign a host to a group within the Mezmo web app. To use tags, make sure the agent is installed on your host, and use this command to add a tag or tags:
You can also edit the LogDNA configuration file, etc/LogDNA.conf or /etc/LogDNA.env, depending on the agent version, and specify the tags there. Even if your hostname or host machine changes, as long as the agent is running with the same tags configured, that host will automatically be added to the dynamic group located under the Hosts filter.

​
How do I override the default hostname?

The Mezmo agent automatically uses the machine’s default OS hostname. If you want to use a different hostname, you can edit the LogDNA configuration file, /etc/LogDNA.conf or /etc/LogDNA.env`, depending on the agent version, and specify the hostname there.

​
Why Does the Mezmo Agent v1 need root access?

The Mezmo Agent v1 works by monitoring changes in local log files (read only access) and sending new lines to the designated ingestion endpoint. These are the primary reasons why Mezmo’s agent requires root access:
  1. The agent listens to kernel-level file events to detect new lines in log files.
  2. The agent monitors default log file paths, such as /var/log or /var/data.
  3. Container-based frameworks such as Kubernetes also use these file paths.
Kubernetes centralized logging, which writes all container logs to /var/log, recommends using a DaemonSet and node-level logging, which is how we implemented the Mezmo agent.