Allow Tokens in Dashboard Names
How about allowing tokens in Dashboard names and descriptions? Currently you can't do this - tokens are only for use in widgets (admittedly that means they can be used on most areas of a dashboard, but left me wondering why they are called Dashboard Tokens and not Widget Tokens). Thanks ! Elizabeth1View1like0Comments
Line separate GROUP token in notification emails
At the moment the ##GROUP## token appears as below in emails. This is very difficult to read as the comma indicating a separate group is hard to spot. Can you please split the ##GROUP## token on the comma and put each one on a new line. Infrastructure Services/Primary/Americas/Network Services/Network Services - Corporate - US/Routers/CenturyLink, Infrastructure Services/Primary/Americas/Network Services/Network Services - Corporate - US/# Locations/Orlando2Views1like0Comments
Create Alert Tokens for Acknowledgement By, and Acknowledgement Comment
Extending alert information from LogicMonitor to other 3rd Party systems is pretty common for us, however, the available tokens today to describe the alert is missing a few bits of data (we feel). It would be incredibly helpful to have an alert token that contains the LM User responsible forAcknowledging the alert, and a separate token for the Ack comment. Having these tokens allows us to better map alerting details to upstream and downstream integrations.4Views0likes0CommentsNew token for Group but without parent path
Please add a new token which interpolates to direct parent group of a device, without the rest of the path (grandparents). So for exaemple, the following: Middleware Services/Database Services/OpenEdge - Global, Business Services/Pacific/Hygiene/NZ/iCABS - Hygiene - NZ would become just: OpenEdge - Global iCABS - Hygiene - NZ Perhaps a ##GROUPWITHOUTPATH##, or something.0Views0likes1CommentString functions for ##token## interpolation
Implement string functions for the Name field. We have very normalized naming conventions and this would save us from having to add multiple items. Example, we have services named: Finance -Corporate - UK Finance -Corporate - FR Finance -Corporate - DE and so on. Would be easier if we could use a string function with token interpolation, especially or the NOC widget, for example: Finance @RIGHT(‘##SERVICEGROUP##’, 2) Where ‘Finance’ is a static, and the function @RIGHT() returns the right most two characters from the ##SERVICEGROUP## token interpolation for each matched item. The end result would be NOC blocks with labels: Finance UK Finance FR Finance DE Hope this makes sense.0Views1like0Comments
Services - Make ##SERVICERESPONSE## available to Overall alerts
I would love it if we could reference ##SERVICESRESPONSE## on an overall alert. We don't deliver alerts for singular test location failures, since our mandate to only notify on systemic issues across all test locations. So the question will probably, which response to include in the event there are differing responses? Why not include all of them! Or only include the first one in the test location array for that service. Or pick a random one. Or arbitrarily decide certain failure reasons have a "higher" priority than others and choose the "highest" one.1View2likes3Comments