Ali Holmes

LogicMonitor Staff
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Ali Holmes

  • Rank

Recent Profile Visitors

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

  1. @mnagel this is in preparation for the change. Full functionality will be available in the next few releases - keep an eye on release notes for that announcement
  2. @Mosh we'll get this fixed in v102. Thanks for the feedback!
  3. Hi all, This has been prioritized again for 2018. To provide a little background: Changing the way data is displayed in the UI is relatively easy, but once data is outside of LogicMonitor (i.e. alert messages, report content) it is no longer dynamic. To change content based on recipient is much more complex, and we don't have a good solution for this (yet). The last thing we want to do is create inconsistencies that further complicate the issue we're trying to solve, which is why this project was put on hold in the past. We know how important it is to support our customers with global resources, we just want to make sure we do it right. With that in mind, and to ensure things go smoothly this time around, we are considering approaching this in phases: 1. Ability to view data in the UI (dashboards, devices, alerts) in user-specific time zone. All configuration operations (scheduling SDT, escalation chains, report delivery, report content, etc) are still done in the account/global time zone (this would be explicitly indicated in the configuration window). Alert messages (i.e. ##START## token) also remain in the account/global time zone. 2a. Ability to configure events (SDT, escalation chains, collector upgrade, report delivery, etc) in user-specific time zone (or possibly user-specified time zone via time zone picker). Each configuration will record and display in the time zone it was set in. 2b. Ability to configure report content (SLA period, time range, etc) in user-specific time zone (or user-specified). Resulting report will be the same regardless of recipient. 3. Ability to receive alert messages and reports in recipient's time zone. We're interested to hear your feedback in terms of these phases as we work through the requirements. What is your highest priority? What percentage of your problems are solved by phase 1 alone? What are your biggest concerns? If alert messages are in a different time zone than your portal data, how does this affect your workflow? If you prefer, you can shoot me an email at -Ali
  4. Hi @mnagel, I have both of these improvements included in the requirements for phase 2. Design is almost done, release will likely be v102.
  5. Hi @ErnieC, our Product team went through a reorg in May that resulted in a significant shift in priorities. I can assure you that this is in development and slated for v99 (phase 1) if all goes smoothly.
  6. This is something we're spec'ing out currently. It's likely we'll have to limit the dynamic table to a single datasource to ensure columns have the same number of instances, but it sounds like that will be sufficient for the examples provided?
  7. @Idan keep an eye out in v96 for this improvement
  8. @Mosh this is something we are working to correct.
  9. Fair request @Frank Slicer, and should be an easy fix. I will discuss with Development for an upcoming release.
  10. Hi @Gaston Gallant, we are in the design phase for a dynamic top 10 style widget - this is an interesting use case to add to our requirements. I may reach out for more detail as design progresses. Thanks!
  11. Hi @mkqai, there should be a blue 'Feedback' button in the bottom right corner of your portal. Feedback submitted here comes directly to our Product team for review
  12. @Mosh this will be corrected in our next release. Thanks for the input!
  13. @Jeffrey McGovern this is in the works! Keep an eye out for group level tokens/cloning in the next couple releases
  14. Great idea @Mosh, keep an eye out for map styling options in v95