Combining product metrics with Flexboard

If your team uses several WhaTap products at once, gathering only the metrics you need onto one screen is far faster than opening each product's default dashboard separately. This guide explains how to build a cross-product dashboard using Flexboard templates.

When you need Flexboard

• Using only one product → The default dashboard is already enough. You don't need Flexboard.
• Want to view several products together → This is what Flexboard is really for, and this guide is where to start.

What you get from this guide

• A team dashboard that is complete the moment you clone a template
• Work that is about choosing and swapping widgets, not building them
• Sharing with the whole team through a single URL

Prerequisites

• The WhaTap agent is installed and collecting data in the Active state.
• You have the project admin or editor permission.

Step 1. Start from a template

Clone one of the provided templates instead of starting with an empty Flexboard.

1. Select the Dashboard > Flexboard menu on the left.
2. On the Template tab (or + Create from template), select the template that fits your purpose.
   • Application monitoring basics — Centered on app metrics such as TPS, response time, and error rate
   • Server resource basics — Centered on infrastructure metrics such as CPU, memory, and network
   • Incident response summary — Focused on tracking events and errors
3. Click the Clone or Start with this template button.
4. Enter a name: {team name} daily status board (for example, Backend daily status board)

Which template should you choose?

• Application development team → Application monitoring basics
• SRE/infrastructure → Server resource basics
• Incident response team → Incident response summary

If you aren't sure which to choose, start by cloning Application monitoring basics. It fits most teams well.

Step 2. Swap only two or three widgets

The cloned dashboard is already built from common metrics. Changing just two or three of them to fit your team's context is enough.

1. Find a metric that matters most to your team, right-click the corresponding widget or click the ⚙️ icon, and then select Edit.
2. Swap the metric.
   • Example: "Average response time" → the response time of a specific API your team manages as an SLA
   • Example: "Overall error rate" → the error rate of business-critical transactions such as payment or login
3. Change the widget title to your team's language (for example, "Payment API response time").
4. Click the Save button.

Don't overreach

If you try to tune more than ten widgets from the start, it ends up abandoned as "the Flexboard we'll finish someday." Leave the template as it is, change only two or three to fit your team, and share it right away — that is the trick to quick adoption.

Step 3. Share it with your team

1. Click the Share button at the top of the Flexboard.
2. Select the visibility scope.
   • Public to the whole team: Any project member can access it.
   • Specific users: Only the people you invite can access it.
3. Copy the Flexboard URL and add it as a pinned bookmark in your team's Slack or collaboration tool.

Make it the first screen of the day

Making "open this link first when you check monitoring" a team rule noticeably speeds up incident detection.

Checking the result

• The new Flexboard appears in the Dashboard > Flexboard list.
• The widgets from the template refresh with real-time data.
• Teammates see the same screen when they open the shared URL.

Your team's own observation point is complete. Flexboard, which used to feel complicated, has moved into practical use through "clone a template → customize a little."

Next steps

• Connect threshold alerts per widget → Attach your first alert
• Want to design widgets yourself → Advanced Flexboard in the stage 2 scenario guide (coming soon)
• Extract the dashboard as a periodic report → Performance reporting scenario
• Merge several projects into one Flexboard → Building an integrated Flexboard (advanced)