Locked
Discussion interactions are currently paused.
More Easily Include and Customize Values/Instances/Formatting in DataPoint's Alerts customized Body Templates
Due to difficulties that caused me to propose: https://support.logicmonitor.com/entries/35788800-JDBC-DataSource-Active-Discovery-SQL-Statement-Parameters-multiple-columns
We subsequently had issues with trying to format the DataPoint's Alert's customized Body Templates the way we want.
As we discovered:
- we can include any tokens in there (including WILDVALUE): http://help.logicmonitor.com/using/datasource/creating-datasources/defining-datapoints/tokens-available-in-alert-messages/
- there are no functions available to be used in that box (especially those of interest to us were advanced string parsing)
- the values that come back from a concatenated JDBC SQL Query can be put in entirely, but not easily parsed to create a "Support-friendly" format
- no possible way to pass in the result of the actual JDBC collector attributes query into the DataPoint Alert Body Template, so we couldn't work around by providing a different query
- even when using ##VALUE##, it will always be the Alert's innate value and NOT any other value that comes back (example: writing a Groovy Script to return a different value in a Complex Datapoint will not replace ##VALUE## with its value, so we couldn't even work around it with this; as per discussion with LM engineering/support)
- Hardcoding a message would only limit the usefulness of the alert and the result would only slow down debugging/investigation
So, this is just a proposal for some easier way for custom data to be passed in to the alert body template.
