Blog Post

Camp LM Blog
1 MIN READ

Week 2 Discussion: Dashboards

skydonnell's avatar
skydonnell
Icon for Community Manager rankCommunity Manager
20 days ago

Hey everyone! 👋

You’ve just explored how LogicMonitor Dashboards help you visualize, analyze, and act on critical infrastructure data, especially when dashboards are designed with purpose, reusability, and audience in mind. Now it’s time to reflect, share your takeaways, and learn from each other.

👉 Discussion Prompt

Share your answers, ask follow-up questions, or jump in to help others troubleshoot. Whether you’re new to dashboards or already building for multiple teams, your insights can help others, and you might walk away with fresh ideas too. Let’s learn from each other and build smarter, more actionable dashboards together!

  • How do you plan out a dashboard?

  • Which widget is your go-to, and why?

  • What do you prefer: cloning existing dashboards or building from scratch?

  • What’s one best practice from the course that you’re planning to implement (or already advocate for)?
Published 20 days ago
Version 1.0

3 Comments

  • Cole_McDonald's avatar
    Cole_McDonald
    Icon for Professor rankProfessor
    18 days ago

    This module is the main reason I wanted to do this camp... I've often said, I prefer LM purely based on the power of the dashboarding.  Living in the SMB MSP world, cost prohibits logs and edwin thus far, but  Dashboarding has allowed me to create "products" that our teams can leverage to perform their duties across many customer environments without leaving the single page... Cross-Tool properties have allowed me to use that starting point to link out to our RMM, Ticketing, and ITSM tools.

    I know it's basics, but going back to the basics every once in a while can help refocus efforts.

    • Cole_McDonald's avatar
      Cole_McDonald
      Icon for Professor rankProfessor
      18 days ago

      Simple design rules I follow for dashboards:

      • format for display defaults on a standard business issued laptop
      • Left -> Right, Top -> Bottom design
        • Most important At-A-Glance up top (NOC Widgets)
        • Next most important below read left to right
      • If the dashboard is "Below the fold", shoulders of the next row of widgets should be visit to hint that there is more to see below.
      • Most important data should never live below the fold.  That's for details.  Scrolling is the enemy of MTTR / Quick answers for clients on the phone while you're looking
    • Cole_McDonald's avatar
      Cole_McDonald
      Icon for Professor rankProfessor
      18 days ago

      Also... we use inherited properties to drive filtering down to specific clients/sites/devices to aid in the troubleshooting efforts.