OSHI Reports Network Interface Error When OpenSearch Container Is Named manager

What?

Graylog is logging the following error repeatedly:

`2026-08-26 08:41:24,164 ERROR: oshi.hardware.common.AbstractNetworkIF - Socket exception when retrieving interface information for name:manager (manager): No such device (getFlags() failed)`

Our Graylog and OpenSearch instances are running as separate Docker containers. The OpenSearch container is named manager, while Graylog is running in its own container.

It appears that OSHI is attempting to retrieve network interface information for manager and interprets the Docker container hostname/name as a network interface. Since manager is not an actual network interface inside the Graylog container, the lookup fails with:

No such device (getFlags() failed)

Why?

Although this does not appear to prevent Graylog from operating normally, the error is misleading and unnecessarily pollutes the Graylog logs.

In a Docker environment, container names are commonly used as hostnames for service-to-service communication. In our setup, for example, the OpenSearch container is simply named manager.

It would be useful if OSHI/Graylog could correctly distinguish between network interfaces and hostnames/container names, or otherwise avoid logging this as an ERROR when the name does not represent an actual network interface.

Ideally, Graylog should either:

Ignore hostnames/container names when collecting network interface information, or
Handle the failed lookup gracefully without producing an ERROR, if the lookup is expected to fail in containerized environments.

This seems particularly relevant for Docker and other containerized deployments where hostnames and service names are frequently used for communication between containers.

Your Environment
Graylog Version: 7.1.8
OpenSearch Version: 2.19.4
MongoDB Version: 8.2
Operating System: Docker (Ubuntu 24)
Graylog Deployment: Docker container
OpenSearch Deployment: Docker container
OpenSearch Container Name: manager
Browser version: Brave latest

Start with OSHI's AbstractNetworkIF handling of the interface name manager and reproduce the Graylog Docker setup described in the issue. Trace why the container hostname is treated as a network interface, then verify that the lookup is handled without a misleading ERROR while genuine interface failures remain distinguishable.

Written by the indexing model from the issue text.