CoreOS

The Middleware Infrastructure Agent collects telemetry from Fedora CoreOS nodes. Its container-based deployment is managed by systemd through Butane configuration, keeping monitoring setup in the host provisioning workflow.

The Agent runs as a container managed by a systemd service defined through your Fedora CoreOS Butane configuration.

Prerequisites#

Before installing the Infrastructure Agent on Fedora CoreOS, make sure you have:

• Butane — Required to convert human-readable Butane configuration files into machine-readable Ignition configurations.
• A running Fedora CoreOS node — The node must have Docker available to run the Middleware Infrastructure Agent.

Installation#

variant: fcos
version: 1.5.0
systemd:
 units:
   - name: mw-agent.service
     enabled: true
     contents: |
       [Unit]
       Description=Middleware Agent
       After=docker.service
       [Service]
       Environment="MW_API_KEY=<MW_API_KEY>"
       Environment="MW_TARGET=https://<MW_UID>.middleware.io:443"
       ExecStart=/usr/bin/docker run \
         --name mw-agent \
         --privileged \
         -e MW_API_KEY \
         -e MW_TARGET \
         ghcr.io/middleware-labs/mw-host-agent:master
       Restart=always
       [Install]
       WantedBy=multi-user.target

butane your-configuration.bn > ignition.ign

MW_HOST_TAGS=key1:value1,key2:value2,... MW_API_KEY="<MW_API_KEY>"

docker ps -a --filter ancestor=ghcr.io/middleware-labs/mw-host-agent:master

Manage the agent (Commands)#

Middleware agent runs as a systemd service in Linux based systems, usually on Linux systems, the Middleware Agent runs as a systemd service. The service definition is typically located under:

/usr/lib/systemd/system/

Use the following commands to start, stop, restart, and check the status of the Middleware Agent.

Verify data collection#

After installing the Agent, allow a few moments for the host to start reporting telemetry.

Go to Infrastructure Monitoring → Hosts and verify that your Linux host appears and is reporting metrics.

After data collection starts, you can:

• View host metrics in Infrastructure Monitoring.
• View collected host logs in Log Monitoring.
• Create alerts for collected metrics.
• Create custom dashboards to visualize Linux host metrics.

Uninstall#

If you need to remove the Middleware.io Infra Agent from your Fedora CoreOS host, follow these steps:

sudo systemctl stop mw-agent.service
sudo systemctl disable mw-agent.service

sudo rm /etc/systemd/system/mw-agent.service
sudo systemctl daemon-reload

docker rm -f mw-agent

docker rmi ghcr.io/middleware-labs/mw-host-agent:master

Troubleshooting#

Data is not coming after agent installation ?

It may take a few moments for telemetry to appear after a new Agent installation. First, go to Infrastructure Monitoring → Hosts and check whether the host is reporting data.

If the host does not appear or data is not being collected, check the following:

Check network connectivity. Verify that the host can establish an outbound HTTPS connection to: https://<YOUR_UID>.middleware.io:443

Check for multiple Agents. Make sure only one Middleware Infrastructure Agent is running on the host.

Check Agent logs. Review the Agent log file for errors: /var/log/mw-agent/mw-agent.log You can also inspect the service logs using journalctl.

Check proxy configuration. If the host is behind a corporate proxy, verify that the required HTTP_PROXY and HTTPS_PROXY environment variables are configured correctly and that the proxy allows connections to Middleware.

Check permissions. Make sure the installation and Agent management commands are run with sufficient privileges. Use sudo where required.

If you’re still unsure about the issue , you may reach out to Middleware support team via chatbot (which you are seeing at right bottom corner of this page) or email at support@middleware.io.