Issues after updating site 2.3 -> 2.4

Troubleshooting
1

CMK version: cee 2.4.0p15
OS version: RHEL 8.10

Error message:

image
image1581Ă—330 33.6 KB

Hello,

We have updated our production from 2.3 to 2.4. Now we have two open issues regarding graphs. Firstly, we occasionally see an exception when we hover over the graph icon at file system service. When you click on the icon, you can see the graphs and the exception disappears.

The second issue is that, at least on Windows systems, a diagram is now missing, namely the free space diagram:

image
image1584Ă—605 95.4 KB

Has this diagram been removed in general, or could it be related to the exception?

Can someone check whether the Free Space diagram is still available on Windows systems? (Backend should be on 2.4).

And can anyone comment on the exception?

Many thanks in advance!

Christian

2

None of our Windows servers show a “Free Space” graph — only a “Used Space” graph is available on 2.4.0p11.

Could this behavior be related to the threshold type (used vs. free space)?
We usually configure “used space” levels. Does the selected type determine which graph is displayed?

3

Hi Lars.

In 2.3 there is the free space graph available. I double checked it in my environments. At 2.4.0p15 I get no exception like this. Looks like that some data missing to render.

RG, Christian

4

I find out that no graph decription is in 2.4. I looked at ~/lib/python3/cmk/plugins/collections/fs.py and there the definition is missing.

It coould be, that the browser cache miss this graphan raise the exception.

My solution th get the graph back:

  • Create a directory with mkdir -p ~/local/lib/python3/cmk_addons/plugins/collections
  • Create a file name “fs.py” or similar and add the following code in it:
#!/usr/bin/env python3
# Add the free space graph

from cmk.graphing.v1 import graphs, metrics, Title

UNIT_BYTES = metrics.Unit(metrics.IECNotation("B"))

graph_fs_free = graphs.Graph(
    name="fs_free",
    title=Title("Free space"),
    minimal_range=graphs.MinimalRange(
        0,
        metrics.MaximumOf(
            "fs_free",
            metrics.Color.GRAY,
        ),
    ),
    compound_lines=[
        "fs_free",
    ],
    simple_lines=[
        metrics.WarningOf("fs_free"),
        metrics.CriticalOf("fs_free"),
    ],
    conflicting=["reserved"],
)
  • Now run omd restart apache && omd restart redis

RG, Christian

1 Like
5

@martin.hirschvogel : Why is this graphing for fs_free missing in 2.4?

1 Like
6

We cleaned up some graphs from 2.3 to 2.4 with the migration on our side to the new Metrics API.
I will ask a colleague to take a look at it

7

Hi Martin,

For your information, free_space is also displayed in the “Size and Used Space” chart, but it’s often barely noticeable on very large file systems. My colleagues actually look at this chart frequently because it allows you to quickly see the development of free_space.

And if the diagram has been removed, is that mentioned anywhere in the werks? I couldn’t find it there, so it’s unclear whether it’s a bug or intentional.

regards

Christian

8

Hi,

As mentioned by Martin, in Checkmk 2.4 we cleaned-up some of our graphs as part of the migration to the new Metrics API. This included removing the ”Free space” graph because its data is already fully covered by the “Size and used space” graph. This change helps to reduce redundancy.

image
image1549Ă—718 61.1 KB

Please note that you can still manually build the “Free space” graph on your own if your workflow requires it.

Regards,
Mathieu

9

Hi Mathieu.

I agree with you to clean up some things. But this need to be anounced. We as a partner get these errors and spent a lot of time to find these problems and fix it.

As an idea: Put the cleaned graphings in a mkp collection of old graphs, so the user can decide if he need it or not, or put it in a werk to find it faster.

RG, Christian

10

With the result that the current graph is sometimes really broken. See this discussion here –> Filesystem graphs exceed 100%

1 Like