elabit/robotmk

Robot framework service discovery level - node whitelist

kkensy opened this issue · 3 comments

kkensy commented

How about allowing a whitelist for nodes in the 'Detection level of services from robot output' parameter of the 'Robot framework service detection' service discovery rule?

simonmeggle commented

Thanks for the suggestion! Do you really have a use case for a whitelist here?
I always thought that a blacklist is sufficient here...

kkensy commented

It's not really a good use case 😅 - we stumbled across this after we tweaked our robot. We moved the keywords into login, navigation, and teardown tasks - renaming them multiple times. We wanted only two of the tasks to show up as checkmk services without editing the blacklist after each tweak and ended up using a regex like ^[^V] . Both monitored test cases start with a "V" and test the status of a system component.

simonmeggle commented

Ah, I see.
I would strongly suggest to have ramp-up work as well as cleanup-tasks in Test Setup and Test Teardown keywords.
In this way you can have as many tests as you want - Robot Framework will do the Setup and Teardown work for every test.
Seems like overkill but has the bis advantage that you can start tests individually and make use of the "Failed test re-execution" of Robotmk.

  • 👍1