Share your Catchpoint Dashboard
Summary: Gerardo Dada, Gerardo Dada, initiates a discussion about observability teams and their reliance on specific dashboards or monitors for daily operations. He invites others to share their most-used dashboards or monitors, emphasizing the importance of these tools in monitoring incidents and starting the day. Gerardo shares his personal favorite: a workforce experience dashboard that displays global experience scores by application and location. He encourages participants to share their own favorites and any customizations or useful tips that benefit their teams, suggesting the use of screenshots if possible.
Every observability team has a few dashboards or monitors they rely on daily. These are the ones you check first thing in the morning with your first sip of coffee or that help you quickly zero in on what matters whenever an incident arises.
We’d love to learn from each other by sharing what works well in your environment. Maybe you can share some of the following:
Which dashboard or monitor do you use most often, and why?
What’s the first thing you look at when starting your day?
Are there any tips, scripts, tests or views you think others would benefit from?
Have you customized a dashboard that your team finds especially helpful?
If you can, share a screenshot!
My favorite is (not StackMap, but that's my second best) the workforce experience dashboard that shows global experience scores by application functionality and by office location with the map. This is our demo environment, of course, but many customers use this as 'mission control' for their workforce experience.
What is your favorite and why?
Gerardo Dada
AdminOP6 months agoSerendipitously, Wasil Banday, one of our value engineers, just shared this dashboard on Linked In for "One of the Internet’s Most Visited Weather Homepages" that focuses on cost optimization.
You can see the full post on LinkedIn.
- Massive traffic (billions of pageviews).
- Global audience.
Most conversations around pages like this are about speed and fairly so, since third-party overhead makes them heavy and slow.
But almost none are about delivery cost.
Let's pause and do the simple math:
• 100+ requests every time someone loads the page
• Billions of pageviews
• A meaningful portion of traffic bypassing cache
Even with very conservative assumptions, that turns into:
- hundreds of dollars per million pageviews becoming hundreds of thousands of dollars a year
- Not because the CDN is “bad” or something is broken.
- But because CDN efficiency is something you have to actively manage and most teams stop looking once things are “working”.
- The blind spot is when delivery inefficiency quietly becomes part of the business model by default.
Backend dashboards look healthy. Finance reports don’t flag it. The bill still gets paid.
And leadership often never realizes this was a choice made implicitly, not deliberately. At this scale, not looking is also a decision.