10 years ago
/* or not to /*
Hi,
Sometimes you need to enter a /* wildcard and sometimes you don't. It's really annoying when you select a group you kind of expect it to add the wildcard for you.
Please could you fix this?
Hi,
Sometimes you need to enter a /* wildcard and sometimes you don't. It's really annoying when you select a group you kind of expect it to add the wildcard for you.
Please could you fix this?
Annoying isn't it. I have put several requests in for this. It's not so bad for me who uses LM every day, but trying to explain to other people to put a /* sometimes and not others is a nightmare! They are always just typing the customers name in the alerts tab and then telling me Logic Monitor is broken because it doesn't show any alerts.
We're working on cleaning this up right now. We will have an indicator for fields that support /* - so you can get just the main group without it, or know if you need to use it. We're also working on ensuring standardized behavior throughout the app for selection fields.
Give us a couple of weeks, and please use the feedback button if you encounter areas where this is happening. We'll make sure they're on the checklist.
Any update on this from LogicMonitor? This is extremely annoying.
We've added a lot of functionality around this recently. Alerts now has an option to include subgroups, which handles the "*" for you. Widget fields all indicate whether or not * is supported, and depending on how the widget data is aggregated the use of glob varies. If you can give us more specifics around where the confusion remains, we'll take another stab.