Fake node used as container for aggregate values
-
I have a node used as a "fake" switch to collect all the traffic generated from a group of virtual machines. That node is configured with the IP 0.0.0.0 so it has no interface. Everything works fine in the data collection, except that the node persists in the "Unknown" status.
Is there a way to force its status to "Normal"? I'm not interested in its "real" state since it hasn't a real state: is just a container for the aggregated values computed from other nodes.Maybe I'm just using the worst approach to solve this problem, any other suggestion is welcome!
Best regards,
Marco
-
Just answered same question in another thread, seems as common problem
Currently the only workaround is to keep active alarm of "Normal" priority on that node. You can create rule to create alarm for that node and post required event from the script using PostEvent function.Best regards,
Victor
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login