For the "License expiring nearing" rule, we created a new configuration.
Set the threshold value as 1 min and selected the f5 device
we tested with providing low value of 1 min
Also provided with high value of 995 days
And also provided the default config value of 55 days
In all the 3 scenario, the alert is not getting generated.
Help in the correct threshold value to be provided to generate the alert.
Hi,
As far as I can tell. F5 licenses don't have an expiration date.
They do have "Service Check Date" that is handled by the rule: "F5 Devices: Service check approaching".
This rule does not have a threshold for trigerring before the relevant date is reached.
Gautam,
Thanks for reaching out to us regarding this ask. Based on the details provided, I think the issue here is that F5 doesn't have license expiration but rather Service Checks. You can search rules by device type, F5 devices for example, locate 'Service Check Approaching' then configure from there. Please note that this rule will not trigger an event before the relevant date is reached. One method I've seen that worked well for others was to create a rule that triggers a warning at 90 days before expiration, and then a Critical message if it's 20-30 days before requiring service. I've attached examples of how to search for rule by device type.
SEARCHING RULES BY DEVICE
SEARCHING RULE BY NAME - NOTICE DEVICE TYPE IN RULE OVERVIEW > CATEGORY
Please let me know if you have any additional questions.
Cheers,
Paul
Does F5 have that check? I couldn't find metrics license-expiration for F5.