Docker Disk IO SUMMARY missing after docker (re)start

dnLL · January 11, 2024, 3:16am

Similar to Disk IO SUMMARY Docker Container, this bug has been in Checkmk for as long as I can remember (so that would be 1.6 where the docker plugin first made its apparition). The Disk IO SUMMARY service eventually gets discovered correctly for my dockers, but if a docker restarts, the service will go to UNKN until some write are made within the docker. It’s certainly annoying as depending on the containers, it sometimes can take a couple of seconds (or minutes) before any disk IO actually happens.

dnLL · January 15, 2024, 2:16am

Is there any setting I could use in WATO to force the service to be discovered even if there is no IO after a container is restarted, or do I need to edit the docker plugin?

dnLL · January 16, 2024, 3:14am

I assume I would need to edit this plugin. Not sure where to start however.

github.com

Checkmk/checkmk/blob/09443f2269023132135ce30801f41e4fc25ebd01/tests/unit/cmk/base/plugins/agent_based/test_docker_container_diskstat.py

#!/usr/bin/env python3
# Copyright (C) 2021 Checkmk GmbH - License: GNU General Public License v2
# This file is part of Checkmk (https://checkmk.com). It is subject to the terms and
# conditions defined in the file COPYING, which is part of this source code package.


import pytest

from tests.unit.conftest import FixRegister

from cmk.utils.sectionname import SectionName

from cmk.checkengine.checking import CheckPluginName

from cmk.base.plugins.agent_based.agent_based_api.v1 import (
    IgnoreResultsError,
    Metric,
    Result,
    Service,
    State,

This file has been truncated. show original

Basically I’d like to be able to force the Disk IO Summary discovery even if there is no activity (with values set at 0).