Forum Discussion

jcayton252's avatar
2 years ago

Overview and Alert Map Dashboard Resource Count limitation

Our customer is a 300+ site, ~2500 resource count entity and currently we can only see addresses for I’m assuming the first alphabetically 400 resources on the Overview and Alerts Map Dashboard.  Anyone else submitted a “feature request” aka Feedback here by chance?  I can’t find an existing topic.  We had this with our previous platform, which was quite limited technically compared to LM.  

Either way, we’d like to see all site addresses and active alerts on our overlay maps for a quick view of global health. 

  • Thanks for the feedback! We also do have the Header graph that’s available on the Alerts page that will group and show alert counts based on the selected dimension. 

    We have the same issue as @jcayton252 and a summarization like this does not meet the needs. We have a retail client that has several hundred locations across the US, not counting international, and they want a map that shows each location and the highest level of alert there. We cannot deliver this properly because of the limitation.

    @jcayton252 the way we did this was speak with the client and got their regions, then used dynamic groups and did 3-4 map widgets to a dashboard. 1 for each region.

  • Sarah_Luna's avatar
    Sarah_Luna
    Icon for Product Manager rankProduct Manager

    Thanks for the feedback! We also do have the Header graph that’s available on the Alerts page that will group and show alert counts based on the selected dimension. 

  • We are having the same problem for a global network monitoring group. We have right under a thousand resources spread out over 25 locations today, but will probably end with about multiple thousand of resources and under 100 locations. It less desirable for us to use 3-4 map widgets as done earlier in this thread to solve this problem, as it still needs to be all shown on one dashboard with multiple other widgets. The Header graph wont work either as it removes important information about where a problem has occurred. We will move over to using resource explorer to fulfil this need as a compromise, as the names of our resource groups are good enough to show where a problem is geographically. We noticed we could also have solved this with services with locations data added to them, but that would have been a lot of work be able to implement and operate.