Hello,
Here re-proposing an old topic only found in Sensu Classic (Using a single check definition to monitor multiple items).
Is there a way in Sensu Go to not create multiple check definitions when having to check multiple items on a server (i.e. websites, ssl certiificates, etc.)?
Hey!
This might be a good use case for using proxy entities with a common attribute key defined each with unique attribute value defined. Then the check would use token substitution to reference that attribute.
Give the proxy request pattern a try, if you run into problems ping me here in this thread and I’ll try to run up a working example for you that you can adapt.
-jef
I believe this is what Jef is referring to:
1 Like