Monitoring files with fileinfo

General
1

Hello All,

I configured the fileinfo file in the .yaml file on a Windows server.
I was able to see the desired files in Check_MK. I used two rules: Size, age, and count of file groups and Group patterns.
What I wanted to monitor was if files with the .tif, .tiff, and .pdf extensions were present for more than 30 minutes. This triggered an alert so action could be taken and the files could begin moving again. The files typically remain in the folder for no more than 2 to 5 seconds. [The reporting time parameter has now changed to 15 minutes.]

Today, the parameter was met, and Check_MK didn’t report anything; the alert remained green. The files being queued (more than 180) no longer met the Group patterns rule; they were added as alerts.

Could you help me determine what the error could be?

This is the configuration in the .yaml file, after editing it I restarted the Check_MK agent on the Windows server that I need to monitor the path and files.

fileinfo yaml
fileinfo yaml1014Ă—427 146 KB

**[Group pattern] This is how I have the rules configured [I have three rules configured, I need to monitor three types of files that are on the same server and in the same path]

imagen

imagen
imagen878Ă—127 8.87 KB

imagen
imagen899Ă—141 9.39 KB

**[ Size, age and count of file groups] This is how I have set up the three size rules:
Configure three rules like the one in the image, just change the extension at the end.
f:\CA-Apps\MDC_TPCAP\CNB_DCDROP_PROD*.TIF
f:\CA-Apps\MDC_TPCAP\CNB_DCDROP_PROD*.TIFF
f:\CA-Apps\MDC_TPCAP\CNB_DCDROP_PROD*.PDF

imagen
imagen1009Ă—1106 48.2 KB

Thanks in advance.

Regards,
Vix

2

The warn and crit levels are set for ages below 14 and 15 minutes.

If I read scenario correctly, shouldn’t it be above by using Maximal age?
image

Not sure about oldest or newest file part.

Edit: maybe the whole file group is not logical in this situation, since you are not interested in the oldest or newest of the file group, but any file that is older than 14 or 15 minutes.

So maybe have a look at Setup > Services > Service monitoring rules > Size and age of single files rules instead.

Probably something like this, but different folder condition:

image
image908Ă—565 34.5 KB

3

Hello Yggy, Thank you for your response.
When there were more than 150 files in the folder, the rule was set to Maximum age of oldest file. The status didn’t change from OK to Critical, and they lasted longer than the established time. Furthermore, the alerts weren’t grouped into the file group object but as separate alerts.
I have now returned the parameters to Maximal age.

Any other ideas?

Regards,
Vix

1 Like
4

not sure if I remember correctly, but I think the python module doing the fnmatch for windows wildcards (which is the default for the include pattern in the file grouping patterns) is case sensitive. So if you group by “*.pdf” but all your files are called “*.PDF” they pattern wouldn’t match and you get single file services instead.