Products

aixbeat
AIX metrics in Elasticsearch

Short answer

aixbeat is a Mentat product that streams metrics from IBM AIX hosts into Elasticsearch. It ships nine datasets (CPU, memory, paging, disk, filesystem, network, host, LPAR, and the agent’s own health), and each one lands in its own Elasticsearch data stream. Because LPAR data is collected next to the host metrics, you can read host metrics in the context of the logical partition they came from.

AIX still runs core systems for many enterprise and government teams. It is also often the one platform that does not show up in the observability stack the rest of the estate uses, so teams end up with separate tools, scripts, and spreadsheets for their Power systems.

aixbeat closes that gap. It puts AIX metrics in Elasticsearch next to everything else you already watch, so the same people can search, chart, and alert on them with the same tools.

Book an Assessment Talk to Mentat

Why it exists

AIX observability that sits with the rest of your estate

Most observability stacks are built around Linux, Windows, containers, and cloud services. AIX hosts get left out, or they get watched by a separate tool that only a few people know how to read.

aixbeat sends AIX metrics to Elasticsearch, so your AIX hosts show up in the same place as the rest of your infrastructure. It is LPAR-aware: partition data is shipped as its own dataset next to the host metrics, which matters on IBM Power, where a CPU number means little without knowing the partition it came from.

One place to look: AIX metrics sit in the same Elasticsearch cluster as your other infrastructure data.
LPAR context: logical partition data is collected alongside CPU, memory, and the other host metrics.
Standard data streams: each dataset is written to its own Elasticsearch data stream instead of a custom index layout.
Agent health included: aixbeat reports on its own health, not just the host’s.

What it ships

Nine datasets, in plain language

aixbeat collects nine datasets from each AIX host. Here is what each one tells you.

cpu

Processor utilization on the host, so you can see how busy it is over time.

memory

Memory usage on the host, so you can see memory pressure building.

paging

Paging space use, an early sign that a host is short on memory.

disk

Disk input and output activity, so you can spot disks that are working hardest.

filesystem

How full each filesystem is, so you can act before a mount point runs out of space.

network

Network interface traffic on the host.

host

Host details that tie every other reading back to a specific machine.

lpar

Logical partition (LPAR) data, so you can read the host’s metrics in the context of the Power partition it runs in.

agent_health

The health of the aixbeat agent itself, so you can tell a quiet host from an agent that has stopped reporting.

How the data lands

Built on Elasticsearch data streams

aixbeat writes each dataset to its own Elasticsearch data stream, following the Elastic data stream naming pattern of type, dataset, and namespace: metrics-aixbeat.<dataset>-<namespace>. For example, CPU metrics from a lab environment land in metrics-aixbeat.cpu-lab.

Elasticsearch manages the backing indices behind each stream, such as .ds-metrics-aixbeat.cpu-lab-2026.10.23-000001. Because every dataset has its own stream, you can search, chart, and manage each one separately, and query AIX data with the same tools you use for the rest of the cluster.

aixbeat is built by Mentat. Elastic and Elasticsearch are trademarks of Elasticsearch B.V.; aixbeat is not an Elastic product.

Getting started

Start with an assessment

To bring aixbeat into your environment, start with a Mentat assessment or a conversation with our team. We will look at your AIX estate, how it is monitored today, and the Elasticsearch cluster you want the data in, then agree how to get aixbeat shipping data.

Cloud Automation Assessment Contact Mentat Platform integrations

Continue exploring Mentat

All Products Cloud Automation Assessment Platform Engineering DevOps & DevSecOps Services Contact Mentat

Frequently asked questions

Questions about aixbeat

What is aixbeat?

aixbeat is a Mentat product that streams metrics from IBM AIX hosts into Elasticsearch. It is LPAR-aware: logical partition data is shipped as its own dataset alongside the host metrics, so AIX hosts can be watched in the same place as the rest of your infrastructure.

What data does aixbeat send to Elasticsearch?

Nine datasets: agent_health (the agent’s own health), cpu (processor utilization), disk (disk input and output), filesystem (filesystem capacity and usage), host (host details), lpar (logical partition data), memory (memory usage), network (network interface traffic), and paging (paging space use).

How is aixbeat data stored in Elasticsearch?

Each dataset is written to its own Elasticsearch data stream, named metrics-aixbeat.<dataset>-<namespace>, for example metrics-aixbeat.cpu-lab. Elasticsearch manages the backing indices, such as .ds-metrics-aixbeat.cpu-lab-2026.10.23-000001, so each dataset can be searched and managed on its own.

Is aixbeat an Elastic product?

No. aixbeat is built by Mentat. It writes to Elasticsearch data streams, but it is not made, sold, or endorsed by Elastic. Elastic and Elasticsearch are trademarks of Elasticsearch B.V.

How do I get aixbeat?

Start with a Mentat assessment at https://www.mentat.cloud/assessment, or contact Mentat at https://www.mentat.cloud/contact-us. We look at your AIX estate and your Elasticsearch cluster and agree how to get aixbeat shipping data.

Bring AIX into view

Get your AIX hosts into Elasticsearch.

Book an assessment and we will look at your AIX estate, your Elasticsearch cluster, and how to get aixbeat shipping data.