Mosh

Members
  • Posts

    594
  • Joined

  • Last visited

  • Days Won

    77

Reputation

159 Excellent

About Mosh

  • Rank
    Myth
    Myth

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. When we setup a new user we have to fetch our default password from a secure password store to input into the new user form. We would like the ability to set a default password that is stored globally in our LM instance and is auto set for new users when this default password is available. A token needs to be made available exclusively for use in the new user welcome email template so that it can be sent to the new user.
  2. We've have been using Dark Reader extension for Chrome browser, which works fairly well, but agree a native dark mode is needed, especially for late night Ops teams and for enterprise situations where users may not have privileges to install browser plugins/extensions.
  3. When viewing a graph or chart I often find I need to view a month's (30 day filter) or a week's (7 day filter) period on the timeline. I then often want to move left or right in the timeline by the same amount, by 30 days or by 7 days. I would like there to be controls on the graph/chart that would "page" (or pan) the viewable time period left or right by the same amount, ie.e 30 days, 7 days, or whatever the current time window width is. (In an ideal world we should be able to simply shift/ctrl + click and drag to pan the chart/graph.)
  4. And the problem with disabling/enabling alerting is that if an operator does it at the wrong level (i.e. accidental on the resrouce object, not an instance) they can accidentally revoke other alerts too. Also, disable/enable does not always work straight away, it can take a couple of goes sometimes I find. So, really, we just want an option on the alert itself that simply removes the acknolwedgement, resetting it back to unacknowledged state.
  5. This is still an issue for us, wonderin if anyone else this problem?
  6. We would like to be able to set SDTs at resource group level using wildcards (or regex). For example, we have a number of event sources for Dyanmics NAV, the names of which all start with "Dynamics_NAV", so we'd like to set one SDT on a group for all the event source that match the expression. Cureently, the only way to deal with this is to have multiple SDTs at the evetn source instance level, which is time consuming to maintain when an SDT needs amending.
  7. Enterprise customer here and I agree this needs fixing.
  8. Another use case today. We have SDTs at a top level group, but now need to move those SDTs down a level in the hierarchy (because SDT windows need to be varied due to change in the business). Now I have to manually recreate them all on th elower level groups. A "Copy SDT From" option would save us time. Out enterprise operates around the globe with business continually reorganizing (M&A, etc), so we're dealing with different timezones, etc. all the time. (We've achieved our end state with the monitoring side of things, so now it's these little Operations productivity enhancements that we're interested.)
  9. It would also be useful to have SDT periods showing on the timeline in graphs (as shaded areas).
  10. Yes, or the platform (resource) may have started life as part of another group and then the business service was changed (application services separated out to different platforms), resulting in a new group to reflect the new architecture of the business service.
  11. @Stuart WeenigHi, yes, an example would be where we have a business service that starts off with one platform, and then one day is expanded to multiple platforms to scale up/out.
  12. Yep, that's right, Stuart. For our use case, it would be fine to simply overwrite any existing note.
  13. Yep, it is super rustrating not having this simple feature! Would be a huge time saver.
  14. What we would prefer is a simple manual options to pin the alert so that if it reoccurs and the alert is already pinned then the count on the pinned alert is incremented. When an alert is unpinned, then the process reverts to normal method of creating and clearing alerts as per DS definition.