ProfessorMike, I think Horace wants these to be different per instance and/or per datasource -- how would you in the current UI define those properties? Perhaps via PropertySources, but then I don't think there is a way to export those as tokens to an integration.
I have gone a different way with my LMKB integration, which is based on Template::Toolkit (but could be any templating system). I have a layout with various standard fragments -- the 'triage' fragment is selected via inherited device property reference, then the article used tokens to conditionally report the correct details. For example, this is a scrubbed sample from an F5 pool check we have been working on:
[% IF lmtoken.datasource.match("Pool State-/Common/foo_") %]
> Typically, when this fails the backend servers are wedged due to Tomcat issues.
[% END %]
The overall output is considered as MarkDown and feeds HTML into our ticketing system. I would much prefer it this was builtin to LM via Groovy, but I couldn't wait :).
