Popular Content

Showing content with the highest reputation since 10/24/2017 in all areas

  1. 2 points
    We are a global company with resources in Minnesota, New Jersey, Australia, Ukraine, and India all using the Logic Monitor tool set. It would be incredibly useful to be able to set the timezone at a user level instead of only at the company level.
  2. 2 points
    I think that this request dove tails with the request to ACL announcements to a role but can stand alone. I would like to have service announcements logged in a central location rather than just having the UI popup banner. Something like Settings --> Account Information --> Platform Messages This way as an MSP if I need to send any information to the user base when the information does relate to them there is the ability pull from an authoritative source. It will also be extremely helpful when you look at the pop up banner and say to yourself that you need to write that information down and then never do and can't recall it when you need it. (Not that I have ever done that. Heard it from a friend)
  3. 2 points
    I'd like to suggest the possibility of adding a "category" to the datapoints. This would assist in alerting and metrics around what types of alerts are occuring. Adding a field to the datapoint would allow us to categorize the type of datapoint for automatic correlation of the events in other systems and as well as provide additional logic for dashboards where you can show alerts based on category type. My idea of default categories would be (not exhaustive, I'd like to see these customizable in the admin area for these to make since for everyone's organization): Capacity Configuration Other Outage/Uptime Performance I've been toying with the idea of adding these just to the alert message template for every alert we have configured and just stripping it out in my automation, but I'm sure there are others that would love to see this as well to help classify the types of alerts that are generated.
  4. 1 point
    Hey LM team, There are a number of options to customize what is in a service alert as well as a data source alert, but config source? Nope, can't modify what gets sent. All it says is that a change was made and gives you a link to the device. A couple things I think would be beneficial as a new feature, 1. Being able to put what lines were added or removed right in the alert. For simple configs you can then tell right away if you need to take action or not. 2. Have the link in the alert actually bring you to the diff view of the current and last config state. While having to click through the multiple links and then slide the diff view slider is fairly painless, at 3am on my phone it can add to the sleepy frustration level. Basically just bringing some of the flexibility that alert templates have for data sources and services to the config sources. Thanks!
  5. 1 point
    Currently, a table must have static columns and rows defined before the widget will display data. It would be great to be able to dynamically build a table's rows based on * To expand on this, it would be great for the table to have the option to exclude instances with zero/no data from the list. For example, I would like a table that displays all MSMQ queue names and the number of messages in each queue - but not display anything if the current queue length = 0
  6. 1 point
    RDP Sessions - ACTXKD Kind regards, Matthew Kerfoot
  7. 1 point
    P2HEZR - Public IP property source Kind regards, Matthew Kerfoot
  8. 1 point
    Currently the graph options for Widget includes three was to "Limit Results". The are "Top 10", Aggregate, All. There are times when I want to display the "Bottom 10". For example the lowest 10 CPU devices, or the 10 least available devices, etc. It would be GREAT to have a Bottom 10" option in the Limit Results parameter. Thanks.
  9. 1 point
    It would be nice if we had a way to invoke a speedtest and record the data pulled down. This could easily be done using a powershell script and a datasource but I'm still fairly new to logicmonitor so creating a data source isn't really something I'm good or comfortable with.
  10. 1 point
    Hi All I've raised a ticket and been told that it isn't possible to stop someone seeing service requests. This presents me with a big issue as an MSP as I don't want the customer base to see improvements that I may productise or features that require additional costs such as LMConfig. Is it possible to add a tick box in the user role to remove this feature? Thanks Marie
  11. 1 point
    Hi Everyone I've hit an issue today that has highlighted 3 issues to me related to use of time-based routing in an escalation chain. I realise that alert routing is 'first satisfied' so you have to squeeze all your required actions into each rule, but what I did not realise and it was not made clear in documentation, only by testing, is that the escalation chain works in list order, not logic not cumulative. In the example below, the second set 'everyday' superseded the third 'Mon Tue Wed Thr Fri'. 1. The documentation doesn't cover this, so nothing tells you that it is neither cumulative or processed in order 2. Being processed in order there is no index or priority order to show you this is the case 3. There is no safety mechanism to prevent, or warning to advise that you are configuring something that doesn't work At least one, and I'd suggest all three of the above should be rectified. As a development request, it would be nice to have cumulative stages as I need to use identical stages across different customers to operate my out of hours service, but also need to include the customer. This would make it more MSP and multi tennant friendly. Thanks Marie
  12. 1 point
    What is the status on this critical feature request? We have started to deploy in Azure all over the world and calculating time differences is way past becoming critical. We expended too many man-hours chasing nothing because the SDT on our CET server was off by an hour because of the 1 week difference in Autumn time changes between EU and US.
  13. 1 point
    I would like to be able to set our account to UTC. Right now we use UTC+-0 Dublin. This causes some users to think this is the dublin timezone (for 6 months of the year with DST that is correct. for the other six months it causes confusion). When set to the current UTC 0 Dublin setting alerts then show GMT in their date time string :-/ Can we please get an option for UTC with no mention of countrys / Citys or GMT?
  14. 1 point
    We have requirement of setting SDT to some servers which are in different time zones. The current time zone setting is portal-wide, so it is not based on group of devices as we require. This would be a very welcome feature for any companies that have sites in multiple timezones, suggest LM should look into this and implement this feature on priority.
  15. 1 point
    Hey James, Another way to do this might be with a property source. If you take a look at this article in the 'From the Front' forum you could do something like create the 'snmp.working=' tag that would then automatically populate once AD runs. This would then allow you to validate based on monitored protocol rather than asset type. The WMI example is pretty easily modified (pull something like winders version) to create a 'wmi.working=' to catch that as well. Cheers!
  16. 1 point
    Agree! We've been doing a lot of work to standardize our DataPoint names as a workaround to not having a category attribute. For example, we would like to categorize all "database" data points, regardless of data source, as database data points. Same for file system data points, regardless of platform OS. We use different middleware solutions, some COTS, some in house, and we'd like to categorize all middleware alerts as such. It would then be awesome to be able to create alerts rules based on the categorization, i.e. all "file system" alerts go to the File System and Storage team, all "database" alerts go to the databases team. This Category attribute of alerts should also be available as a column in the Alert Widget table.
  17. 1 point
    Problem I have a datasource that collects information from the LogicMonitor API. In order for this to work correctly I need a valid user on the LM platform with a valid API token. I can see two potential paths forward. Case 1 - Use my existing account as the datasource author with my API token. This has a big downside that if I have to leave the company for any number of reasons and my account gets disabled this datasource will stop working and is customer facing. This is probably not so good. Case 2 - Create a 'service account' inside LogicMonitor that can have its' own API token and if any one human needs to leave the company there really is not a big problem. The issue with this is that this user has a username and a password that can grant it access to the UI under all the permissions granted by the role but this account should/will never be used within the UI. This also generates a potential security problem because the password will most likely never be rotated because as long as the API user and token work this is simply going to sit there. Request Be able to create a new user type of 'API only' which will never have access to the UI and therefore you should not have to set any of the UI specific information for the account. This would remove the need for any of this information under that account: First/Last name/Email/Password/Force password change/2-factor/Phone/SMS/SMS Email format
  18. 1 point
    There are many times where multiple thresholds make sense for a datapoint, but LM forbids this. Simple examples: * If bitrate is too low OR too high on an interface (especially if one case might be a warning and the other case is critical) * Just ran into this: Cluster Node State on a database server can have different values -- one might be critical and another just warning. If the values are arranged just right, you can fake it with increasing or decreasing values for < or > thresholds. But in this case it is really possible to pick up "not OK" when some of those are more bad than others. What I often do is create tracking complex datapoints with different thresholds assigned, so there is a workaround, but it is awkward. I see no reason that several threshold definitions should not be allowed to be assigned at once if needed. Thanks, Mark
  19. 1 point
    This is great, just implemented. Using for another feature as well in a dynamic group. We have at several times where we'll take major site outages that have 100+ devices, the collectors go a little bonkers with the failed task rates, so we can disable all the datasources and any existing alerts when the device goes dead. Added feature I noticed you're using the hostStatus, maybe we could also use the alertStatus as well, break it up, and say what the highest state of alert the device is as well? Does active discovery run when a device changes alert state as well? Or just when it goes from dead to normal?
  20. 1 point
    This has been asked many times, including by me, but we so far have no indication it is on the roadmap and if so, where. It is an annoying gap, but arguably could be complicated to do properly. But really, if each device has a timezone and you need to display data together aligned to the same actual time, it is not hard to normalize to UTC, then render graphs in the user default timezone or a specific timezone. Hopefully this gets attention soon... Mark
  21. 1 point
    Agree. The current single time zone makes managing SDT across time zones very difficult, especially for us enterprise customers with large IT estates.
  22. 1 point
    I'm not sure where else to post this, but I wanted to make sure the LogicMonitor team takes another look at the apache solr datasources in the repository as they need to be scrubbed. Currently these datasources use applies to rules that seem to be very specific to one customer. Here is one example: contains(system.groups,"SEARCH/CHI/SLAVE/JOB") or contains(system.groups,"SEARCH/AMS/SLAVE/JOB") or contains(system.groups,"SEARCH/QTW/SLAVE/JOB") or contains(system.groups,"SEARCH/CHI/MASTER/JOB") or contains(system.groups,"SEARCH/AMS/MASTER/JOB") or contains (system.groups,"SEARCH/QTW/SLAVE/JobAux") or contains(system.groups,"SEARCH/CHI/SLAVE/JOBAUX") or system.displayname =~ "solrone" I should also mention that I have completely rebuilt these datasources and combined them into a single datasource that pulls all of this data with a single API query. I'll be submitting it after I scrub and polish it.
  23. 1 point
    I upvote this,and suggest the same for web services.
  24. 1 point
    This would be a very welcome feature for any companies that have sites in multiple timezones, b/c as-is alert times are less intuitive and require timezone normalization for everybody except those who happen to fall into in the global timezone. We have all of our locations organized under different top-level host groups, so even allowing it at the top tier groups would solve the problem. Thanks