Week 2 Discussion: Dashboards
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)?
3 comments
Cole McDonald
·1 year agoThis 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
·1 year agoSimple design rules I follow for dashboards:
Cole McDonald
·1 year agoAlso... we use inherited properties to drive filtering down to specific clients/sites/devices to aid in the troubleshooting efforts.