Leaderboard


Popular Content

Showing content with the highest reputation since 05/20/2019 in all areas

  1. 2 points
    I would like to be able to create dashboards where I have the option to create sub-dashboards that I can navigate to. In some of our dashboards, the number of charts or widgets can be high and would cause clutter and confusion. Sub Dashboards would allow us to better organize charts. Of course, provide the ability to navigate back to the parent dashboard(s) too. Also consider allowing alert/color indicator in child dashboards to propogate up to the parent dashboard. If I use a dashboard to depict the health of a business application, I can then see which child dashboard(s) contibuted to the alert and then drill down to see the offending resource(s) that this business application depends on.
  2. 1 point
    Background/use-case: While the ability to click-and-drag to move items around on the Resources tree is absolutely fantastic, we've had a few but impactful occurrences where administrators accidentally moved groups when their mouse shifted slightly while clicking and it threw their target into the group above/below it. While a simple mistake with a simple fix to undo, some accidental moves have gone unnoticed until users report missed alerts due to alert filters/rules no longer matching. The Ask: It would be nice to have the option on groups & devices to prevent the ability to drag-and-drop that specific item (i.e. lock it to its parent group). After a very brief look at the current UI code, it might be as simple as this option not setting the related drag-and-drop CSS classes on that node of the tree.
  3. 1 point
    In the Auto Updates for Collectors, when you set a schedule there is no way to go back and edit the Collectors in that schedule without having to delete the schedule and re-add it again with the new Collectors. Please give us the ability to add or remove Collectors from an Automatic Collector Upgrade Group within the Selected Collectors area. This would make administration much easier than having to delete and create every time I need to add or remove a Collector from an Auto Upgrade.
  4. 1 point
    I too would like to be able to configure the NOC widget so that clicking on the a NOC widget item takes us to another dashboard rather than the resource.
  5. 1 point
    A much-needed feature, pop-up confirmation on drag n drop etc - I would, however, leave out the option to 'do not ask me again' as some people might select that option the first time and then they would be back to the same scenario now. The extra mouse click of a confirmatory action is very minor when comparing the potential consequences of dragging one customer device group into another, especially if individual customer 'ServiceNow' or other integrations have been set up.
  6. 1 point
    I'm currently trying to make a customer facing dashboard that inventories their VM status in a NOC view, then when one is clicked on, rather than going to the resource page (they don't need that much detail) takes them to a dashboard for that resource with specific info on it (CPU, MEM, DISK, etc.). This would be a very helpful feature to add. Perhaps with the ability to define data that gets passed from one dashboard to another to be access with a ##variable## in the sub-dashboard. This would allow the click to pass the ##system.displayname## for instance to allow it to show the data from whatever you're looking for (resource or resource group, specific DataPoint, etc.).
  7. 1 point
    What is the retention period for data in TSDB? How can I fetch data from TSDB if I want to observe a trend over a particular period of time?
  8. 1 point
    We very frequently need to jump between a monitored resource and the collector resource that is doing the monitoring. Please make the system.collectordesc on the Info page of a resource into a hyperlink to the collector resource. This would turn multiple keystrokes/clicks into a single click operation to navigate from a resource to the resource's collector.
  9. 1 point
    The ability to have a SDT "scheduler" like the one below would be helpful.
  10. 1 point
    It would be very welcome (read as: required) that we can mark days as a bank-holiday. During these days we normally have no staff on site and alerting should be done in a different way as on normal working days. Last week we had a production incident which was not routed correctly due to the fact nobody was in the office on Public holiday. My ideal situation would be something like this: 1. Be able to create a custom list of dates (just a single list) on which monitoring should act on in a different way. 2. On the alert rule "time based chain" add an extra "day" besides Mon-Sun (i.e. called special) 3. if an alert arises it should first check if the now() moment is in the special list. It true, act on that. If not continue normal processing. Thanks a lot! Jeroen
  11. 1 point
    In Nagios, there is a concept of an event handler that can run to try to fix problems (e.g., restart a service, remove old files, etc.). I see no similar capability in LM and it is of course something customers want to see happen. For example, I just deployed a custom DS for someone to check for too many files in a share, indicating a service problem. Once I implemented that, the next question was "Can you restart the service when that goes into warning?" I see no facility for this in LM, but perhaps a custom alert could be used to trigger the behavior. If I used that approach, I would insert a custom HTTP alert into the escalation chain earlier on to give the problem a chance to be corrected, then I will have to create a secure REST API server to accept those and trigger the correct behavior. So in theory it could be done (if I am not missing something), but it feels like using a screwdriver to hammer in a nail. Thanks, Mark
  12. 1 point
    I find the Alert Rules really poor so it would be great to see some improvements. The things we would like is the ability to: add multiple Escalation Chains per Alert Rule (otherwise I need to make a different Chain for every Rule) allow multi tenant clients to manage/create there own Escalation Chains and Alert rules Are there any updates proposed for these?
  13. 1 point
    @Michael Rodrigues I had a similar thought. Downloaded tactest from tacacs.net. The cli is straightforward to use. This can be loaded on the primary and backup collectors and run from the script you've mentioned. If we don't figure out an elegant way to test via groovy we will use this method for both tacacs and radius.
  14. 1 point
    Need a Nimble datasource to pick up power supply status. Array Info already uses the cli to gather data, so work needed would be minimal.
  15. 1 point
    Please forgive me if this has been requested in the past. I didn't see it in my brief searching. Background/use-case: Our users and administrators often bounce between several different combinations of filters in LogicMonitor's Alerts tab throughout the day. There are some common combinations of filters used more frequently than others by individuals, by specific teams, and by all users. While we can, and have, created dashboards for some of these common sets of alerts, the dashboard Alerts widget doesn't offer the same functionality as LogicMonitor's main Alerts tab - particularly the inline graphs and history (which are wonderfully useful). The Ask: Allow saving combinations of filters on the Alerts tab as named filter-sets (i.e. favorites), along with a basic interface for managing these filter-sets (editing, deleting, re-ordering, etc). It would also be wonderful to have the ability to designate shared/public filter-sets (controllable by role). I see this as a valuable enhancement for customers not doing event management through external systems. As an additional nice-to-have, it would be very useful to have the option to save column settings per filter-set as well.
  16. 1 point
  17. 1 point
    I've successfully tested using CredSSP delegation as a 2nd hop solution. This is becoming a viable option (of course, but the time I finish, LM will have added it as a simple in UI solution).
  18. 1 point
    You can also try looking up "LocalAccountTokenFilterPolicy" on google. Servers joined to a domain but have a custom local administrators account (aka not the default "administrator") can be blocked by the remote version of UAC. Setting LocalAccountTokenFilterPolicy to 1 will disable remote UAC, which does have some possible security implications (like UAC itself) but might be worth trying as a test atleast.
  19. 1 point
    We have script DataSources that output useful diagnostics information that help Operations to understand the number value when an alert is generated. We want to include the raw output from a DataSource in the alert and email body. What we need is a ##DSRAWOUTPUT## token which contains the complete raw output sent to standard out from a DataSource script. For example, we monitor for processes running under credentials they are no supposed to be running under, and we want to include that info as textual information in the alert/email body.
  20. 1 point
    One of the biggest challenges with LM is the reliance on numbers only in datasources -- the reason is understood, but the result is often messy and many backflips must be done to get a usable result in many cases. I recommend that there be a "lookup" function for numbers that can be associated with datapoints so numeric values can be replaced with text when that is appropriate. An example I just ran into today was after I added the OpenWeatherMap datasource from LM Exchange. It did not include the weather condition, so I added that to the datasource. The values for these range from 200's to 800's indicating "clouds", "rain", etc. You could in theory create a legend for this as is done typically, but the list is too long in practice for 60-odd values (https://openweathermap.org/weather-conditions). If those code-to-string lookups could be defined and referenced, then the value displayed in graphs, in alerts and anywhere else applicable could be displayed as the mapped values, not the original codes. This obviously applies much more widely than this example, but this example shows more clearly how the current method breaks down.
  21. 1 point
    Our Infrastructure team uses the default thresholds on all data sources, and we receive all 'Warning, Error, & Critical" alerts for all data sources. We have various teams that want to be notified on a small subset of devices that use different thresholds than the defaults. Currently, in order to accomplish this, we have to clone the dataset, set the desired threshold settings, and configure a new alert rule to notify the the secondary team. This new alert rule has to have a lower priority set than the default Warning alert. The problem with this approach, is the original default Warning alerts for these devices will not be sent to the Infrastructure team, due to the alert rule for the cloned device having a higher priority. I've worked with other monitoring applications that allow for multiple alert notifications to different teams using different thresholds. It would be nice to have this feature in LogicMonitor.
  22. 1 point
    I need this too. The Alert Rules section is complex enough as it is and it would be really useful to have a description/comment field to document and explain the rule to operators. It would also be good if this description/comment were to appear as a tooltip when hovering over the alert rule name in the alert table, similar to how a DataSource description appears in a tooltip in the device tree.
  23. 1 point
    Because of the of the way Alert Rules are processed, we need a way to export all Alert Rules definitions so that we can store a copy in our Configuration Management ystem, and also so that we can take a backup before implementing major changes to Alert Rules, so that if the change needs to be reversed, we can refer back to the previous configuration of Alert Rules. Yes, of course, we can take screen shots, but that would be very time consuming if we had to update lots of alert rules. A generic Export/Import All Alert Rules option would be ideal.
  24. 1 point