AIX Monitoring

Loki Agent for AIX

Native AIX error log forwarder for Grafana Loki – real-time errpt monitoring with 9 structured labels. Requires only gcc-libs, TLS support, BFF packaged. Centralize AIX error logs across your fleet.

30-Day Returns

aix-exporter tiered pricing

Quantity Discount (%) Price
1 - 10 65 
11 - 49 15.38 % 55 
50+ 24.62 % 49 
Loki Agent for AIX 65 

AIX Error Log Forwarder for Grafana Loki

Loki Agent for AIX reads the native AIX error log subsystem events (errlog/errpt) in real-time and forwards structured entries to Grafana Loki via HTTP or HTTPS. Turn your errpt events into searchable, alertable log streams. Correlate the sequences of multiple errpt events over time and multiple systems and lpars: troubleshoot faster, identify the root causes quicker, gain in agility and reactivity. Installation in one command with installp.

Centralized errpt collection

Instantly monitor the health of your entire AIX fleet

Every LPAR in your AIX fleet streamed live into a single Grafana view. No more SSH-hopping across hosts to chase errpt entries — open one dashboard and see the whole estate at once.

Centralized errpt collection across the AIX fleet in Grafana
Multi-dimensional filtering

Fine search among thousands of events

Filter errpt events on any dimension that matters: hostname, machine ID, error class (H/S/O/U), type (PERM/TEMP/PERF/PEND/INFO/UNKN), resource (hdisk*, ent*, SRC, …), template ID, or description text.

Multi-dimensional filtering of errpt events in Loki Explore
Alert sequence visualization by criticality

Visualize the history of events

Interactive timeline with zoom, acknowledgement, and cross-LPAR correlation, color-coded by severity. Spot the cascade of errors that led to an outage in seconds, instead of stitching it together from raw errpt output.

Alert sequence timeline with zoom and acknowledgement
Syslog compatible

Slot into your existing log stack

Loki Agent runs as a native AIX SRC subsystem with a standard BFF package — no VM, no container, no third-party runtime. Every event is also routed to local syslog, so it plugs into rsyslog, syslog-ng, or any forwarder you already run with zero rework.

$ tail -f /var/log/syslog
Apr 26 09:15:42 aix-prod-01 daemon:notice loki-agent[2851232]: forwarded errpt entry crcid=4B436A3D class=H type=PERM resource=hdisk5
Apr 26 09:15:43 aix-prod-01 daemon:info   loki-agent[2851232]: push to loki ok (1 entry, 312 bytes)
Apr 26 09:15:51 aix-prod-01 daemon:notice loki-agent[2851232]: forwarded errpt entry crcid=754F65F2 class=S type=TEMP resource=fcs0
Apr 26 09:15:51 aix-prod-01 daemon:info   loki-agent[2851232]: push to loki ok (1 entry, 298 bytes)
Apr 26 09:16:03 aix-prod-01 daemon:notice loki-agent[2851232]: forwarded errpt entry crcid=F31FFAC3 class=H type=INFO resource=hdisk0
Apr 26 09:16:03 aix-prod-01 daemon:info   loki-agent[2851232]: push to loki ok (1 entry, 305 bytes)
Apr 26 09:16:18 aix-prod-01 daemon:warn   loki-agent[2851232]: loki unreachable, retry in 5s
Apr 26 09:16:23 aix-prod-01 daemon:info   loki-agent[2851232]: loki reconnected, resuming forward

Workflow

Loki Agent for AIX pipeline: errpt monitor, parse and enrich, push to Loki, query and alert in Grafana

Create your alert rules

Define alert rules in Grafana directly on top of your errpt streams. Trigger on hardware faults, error rate spikes, or repeated failures across the fleet — routed to Slack, PagerDuty, email, or any webhook your team already uses. No extra agent, no second alerting stack.
Grafana alert rule for AIX errpt hardware errors

Push the alerts wherever you want

Configure contact points once in Grafana, then route any alert wherever your team actually pays attention — Slack, Microsoft Teams, PagerDuty, Telegram, email, or any webhook. Match urgency to channel: paging for hardware faults, Slack for warnings, email for digests.
Grafana contact points configured for Loki Agent alerts

Example LogQL Queries

Once data is flowing, you can answer real questions with LogQL. A few examples your ops team will actually run:

# Show all hardware errors across the fleet
{job="aix-errpt", class="H"}

# Find disk-related errors on any host
{job="aix-errpt", resource=~"hdisk.*"}

# Error rate per LPAR over 24h
count_over_time({job="aix-errpt"}[24h]) by (hostname)

Use Cases

Compliance & audit

Searchable historical record of every errpt event across your fleet. Long retention, queryable any time, exportable for audits.

Cross-source correlation

Combine errpt streams with Prometheus metrics from AIX_exporter to tie hardware errors to CPU, memory, or I/O spikes — full picture in one Grafana view.

Faster troubleshooting

Filter and pivot across hosts, classes, and resources in seconds. No more grepping individual errlog files on each LPAR.

Trend & pattern analysis

Spot recurring errors, degrading hardware, or noisy resources over weeks and months — anticipate failures before they cascade.

Specs & Requirements

Operating System IBM AIX 7.1, 7.2, 7.3
Architecture IBM Power Systems (POWER7 and later)
Disk space < 1 MB
Memory < 3 MB RSS
CPU overhead Negligible — event-driven, sleeps between errpt entries
Dependencies None for the standard build (AIX base libraries only). TLS build requires libssl and libcrypto from AIX base OpenSSL 3.
Network Outbound HTTP/HTTPS to Loki (default port 3100)
Grafana Loki 2.x or 3.x
Grafana 9.x, 10.x, 11.x, 12.x

Deploy on AIX in 5 minutes

Standard AIX BFF package, registered as an SRC subsystem with auto-start. Install with installp, manage with startsrc/stopsrc. All configuration in a single file at /etc/loki/loki-agent.conf.

# 1. Install the BFF package
installp -aXYgd /path/to/loki-agent.1.0.0.1.bff all

# 2. Edit configuration
vi /etc/loki/loki-agent.conf

# 3. Start the agent
startsrc -s loki-agent

# 4. Verify in Grafana Explore
{service_name="errpt"} | json
Configuration options
Feature Description
Loki server Hostname or IP of your Loki instance with -s <server>
Configurable port Connect on any port with -p <port> (default: 3100)
TLS encryption Secure connection to Loki with -t flag
Custom API path Override the Loki Push API endpoint with -u <path>
Custom error log path Read from a different errlog with -e <path>
Configuration file All options in /etc/loki/loki-agent.conf
Batch replay mode Parse entire error log history with -b and exit
Syslog integration All events logged to syslog — startup, errors, forwarding status
SRC managed Registered as AIX SRC subsystem — startsrc/stopsrc
Auto-start on boot Inittab entry created automatically
Standard BFF package Native AIX installp installation

Licensing

Perpetual license — pay once, use forever. Per-LPAR pricing with volume discounts. First year of maintenance (updates + support) included.

Frequently Asked Questions

Does it support TLS?

Yes. Enable TLS with the -t flag or tls = yes in the config file. Supports connections to Loki behind HTTPS reverse proxies.

Can I replay historical errpt entries?

Yes. Use batch mode (-b) to parse the entire error log history, push it to Loki, and exit. Perfect for backfilling historical data.

What happens if Loki is unreachable?

The agent logs warnings to syslog and retries. It continues monitoring the error log so no entries are lost. When Loki comes back online, new entries are forwarded immediately.

Can I set up alerts on errpt entries?

Yes. Use Grafana alerting with Loki queries like count(rate({service_name="errpt"}[1h])) by (node_id, class). Route alerts to Google Chat, Telegram, Slack, PagerDuty, or email.

What’s included in the free trial?

The trial is fully functional with no time limit. It forwards all errpt entries with all labels. Try it on your infrastructure before purchasing.

Can I deploy it with Ansible?

Yes. We provide a ready-to-use Ansible playbook for mass deployment with config templating (server, port, period). Deploy across your entire AIX fleet in minutes.

You may also like…