Once the container goes down , its virtual nic become unknow till the time next rescan on the server.
Hallo,
you can configure these service to be excluded from monitoring.
Ralf
Hi, Thanks for the reply.
I dont want to exclude as these are dynamic and I dont know which interface come online next time whenever the the new container runs.
E.g below are UNKN state now,
nterface cali7983e4b65f7
nterface cali7983e4dasa
nterface cali798wdfsdge
nterface cali798a23arwe5
nterface cali79aseavrw3r
and below are online,
nterface cali7kuinhgu
nterface cali7erttsfs45
nterface cali79weaerv
so very to hard exclude as well, as I said these these are dynamic.
Hallo,
1)
the can be configured to use wildcards
2)
Is the info that the interface is up is really important for you?
3)
If the container is static you can check it using end2end checks
Ralf
Hi Ralf,
Kindly find the inline comments…
Hallo,
1)
the can be configured to use wildcards
yes we can use wildcard to ignore but I dont want to ignore anything , which mean certainly I want to ingnore which are in State as “UNKN” but dont want to ignore the one which are live and having state OK
Is the info that the interface is up is really important for you?
Yes, we do want to monitor the interface with container as well
If the container is static you can check it using end2end checks
These are not static container
Overall, I want to ignore the interface which are in UNKN state only.
-anil
I was earlier using the
rule: Network interface and switch port discovery
for Appearance of network interface to "Use Index"
In this case, I was never faced this issues
When I changed the rule: Network interface and switch port discovery to “Use alias” Then these interface which are dynamic and their Alias gets changed and these interface become UNKN.
I have used Rule: Network interface and switch port discovery for Appearance of network interface to “Use Index”
OK Interface 1 [lo], (up), MAC: 00:00:00:00:00:00, Speed: unknown, In: 38.5 B/s, Out: 38.5 B/s
OK Interface 2 [eth0], (up), MAC: 00:xx:56:98:2C:7B, Speed: 10 GBit/s, In: 530 B/s (<0.01%), Out: 1.50 kB/s (<0.01%) 222 s 43.7 s
OK Interface 3 [eth2], (up), MAC: 00:xx:56:98:1E:29, Speed: 10 GBit/s, In: 248 B/s (<0.01%), Out: 48.0 B/s (<0.01%) 222 s 43.7 s
OK Interface 4 [eth5], (up), MAC: 00:xx:56:98:1C:9C, Speed: 10 GBit/s, In: 10.0 B/s (<0.01%), Out: 0.00 B/s (0%)
Now , I have renamed the eth5 to eth1, then I can see the below changes
OK Interface 1 [lo], (up), MAC: 00:00:00:00:00:00, Speed: unknown, In: 38.5 B/s, Out: 38.5 B/s
OK Interface 2 [eth0], (up), MAC: 00:xx:56:98:2C:7B, Speed: 10 GBit/s, In: 530 B/s (<0.01%), Out: 1.50 kB/s (<0.01%) 222 s 43.7 s
OK Interface 3 [eth1], (up), MAC: 00:xx:56:98:1C:9C, Speed: 10 GBit/s, In: 10.0 B/s (<0.01%), Out: 0.00 B/s (0%)
OK Interface 4 [eth2],(up), MAC: 00:xx:56:98:1E:29, Speed: 10 GBit/s, In: 248 B/s (<0.01%), Out: 48.0 B/s (<0.01%) 222 s 43.7 s
Interface Index 3, which was earlier with “eth2” and now the same Index associated with eth1, and Interface 4 is now associated with eth2.
so here index get changes and that is the reason Discovery did not find any UNKN state devices.
But when the same use case tried with Rule: Network interface and switch port discovery for Appearance of network interface to “Use Alias”
then discovery is looking for the Alias and the Alias is not there on systems, but checkMK is looking for the same alias so at the end it give the status as “UNKN” : Item not found in monitoring data
and Check_MK inventory check says "1 unmonitored services (lnx_if:1)WARN, 1 vanished services (lnx_if:1), no new host labels, rediscovery scheduled
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.