Datadog · Monitoring dashboards
Monitoring dashboards in Saudi Arabia: NOC, engineering and management views that people use
A monitoring dashboard is a screen that answers one group of people's questions about your systems at a glance: is the service healthy, where is it slow, is it getting better. Most organisations have plenty of dashboards and few that anyone opens. This guide explains why, what the operations centre, the engineers and management each need from a dashboard, the options and their trade-offs, and where Datadog dashboards fit. Interkey is an official Datadog partner in Saudi Arabia; it sells licences, implements and supports the platform, and sets up dashboard templates with your teams.
Published 9 min read
Orientation
At a glance
The page in one table, for the reader with five minutes.
- What a monitoring dashboard is
- A set of graphs and figures that answers one audience's questions about systems, from live data
- The usual problem
- Many dashboards, built once for one person, that nobody trusts or opens
- Three audiences
- The operations centre (NOC), engineering teams and management, each with different questions
- Where Datadog fits
- Dashboards on the same metrics, traces and logs your monitoring already collects, with templates and role-based editing
- Where it does not
- Finance or sales reporting from business systems, and data that may not leave the Kingdom
- What Interkey does
- Dashboard templates for each audience, tagging, Arabic titles where wanted, and support from Riyadh
In short, for managers
- A dashboard is for a question, not for showing everything that is collected.
- The NOC, engineers and management ask different questions, so one dashboard cannot serve all three well.
- Templates keep dashboards consistent: every service shown the same way, so people learn to read them once.
- A dashboard needs an owner, or it goes out of date within months as systems change.
What a monitoring dashboard is for, and why so many are ignored
A monitoring dashboard turns telemetry, the numbers and records your systems send, into a view a person can read in seconds. A good one answers a specific question for a specific group: is the customer portal healthy right now? for the duty engineer, which release made checkout slower? for a developer, did we meet our service targets this quarter? for a director.
Read more
The common failure is not a lack of dashboards. It is too many, each answering the question its author had that week. Two dashboards show "availability" calculated in two ways. A wall screen shows forty graphs, none of them red, while customers report the service is down. After a few such mornings people stop looking.
Three causes explain most of it: no named audience, so the dashboard tries to please everyone; data not tagged consistently, so one service appears under three names; and no owner after it is built, so it drifts as systems change. A new tool fixes none of these; deciding who each dashboard is for does.
Why it matters for IT teams in Saudi Arabia
Three things sharpen the question in the Kingdom. Many organisations run an operations centre that watches government portals, payment journeys or core systems around the clock, so the wall screen is the first place a failure should be seen. Senior management increasingly asks for service reporting it can read without an engineer beside it, often in Arabic. And dashboards show data, which raises the question of where that data is stored and who may see it.
Read more
On the last point: Datadog is SaaS, so the data behind its dashboards is stored on the Datadog site chosen when the account was created, and as of November 2026 none of its sites is in the Middle East. Our observability data residency guide explains how Saudi estates filter or mask sensitive fields before anything leaves. Sharing needs the same care: a public link to a dashboard is visible to anyone who has it.
IT operations dashboard, engineering dashboard, executive monitoring dashboard
Start from the audience. Each row is a different dashboard, with a different owner and a different screen.
| Audience | The question it answers | What the dashboard shows | Where it is read |
|---|---|---|---|
| Operations centre (NOC) | Is anything failing now, and who has it? | A few health indicators per critical service, open alerts and their status, recent changes; red only when action is needed | A wall screen in TV mode, refreshed automatically |
| Engineering teams | Where is my service slow or failing, and why? | Request rate, errors and latency per endpoint, dependencies, infrastructure behind the service, deployments overlaid on graphs | Laptops, during incidents and after releases |
| Management | Are our services meeting their targets, and is it improving? | Service-level objectives, availability and incident counts per period, trends against last quarter, in plain words | A browser, the mobile app, or a scheduled PDF report |
| Business owners of a service | Are customers completing what they came to do? | Journey success rates, real-user page speed, volumes by channel or region | A shared view agreed with the service owner |
The NOC dashboard should be boring most of the time: if nothing needs action, nothing is red. The engineering dashboard can be dense, because its readers know the system. The executive monitoring dashboard needs no explanation: few numbers, each with its target and trend. For service targets, see our page on SLO monitoring; for what happens once the NOC sees red, see incident management.
Options for building monitoring dashboards, and their trade-offs
Organisations usually arrive at one of four arrangements, often several at once.
1. A dashboard inside each tool
Every monitoring, logging and cloud console has its own screens. They cost nothing extra and teams know them, but nobody sees the whole service: during an incident, people compare graphs across four browser tabs.
2. A separate reporting or business intelligence tool
Read more
Data is exported into a reporting platform the business already uses. This suits monthly management packs, but is weak for live operations: exports lag, and an engineer cannot click from a graph to the trace or log behind it.
3. One observability platform with its dashboards
Metrics, traces, logs and events land in one place with shared tags, and dashboards sit on top, so a graph can be filtered by service and opened down to the request behind a spike. The platform must collect the data first, and its cost follows the data collected, not the number of dashboards.
4. Spreadsheet or slide reports
Someone copies figures into a monthly report. It is simple, but late, manual and only as accurate as the person who prepares it. Most teams keep one for the board, ideally fed from one of the options above.
Before you build a monitoring dashboard
Answer these for each dashboard; they decide whether it will still be used in six months:
- Who reads it, by role, and on which screen.
- The three to five questions it must answer, written down.
- One definition per figure: how availability, error rate or response time is calculated, agreed once.
- A tagging standard for service, environment, team and version, so filters work.
- What turns a graph red, matched to the alert thresholds the NOC acts on.
- The language of titles and notes, Arabic, English or both, decided per audience.
- An owner and a review date, so the dashboard changes when the system does.
Where Datadog dashboards fit, and where they do not
Datadog dashboards sit on the data Datadog already collects for infrastructure monitoring, application performance monitoring, logs and real users. Its documentation describes the features that matter for the problems above:
- Preset dashboards appear for many integrations once they are installed, so a database or cloud service has a starting view on day one. A preset can be cloned and adapted without changing the original.
- Template variables filter every widget at once, so one service dashboard can show any service, environment or region chosen from a list.
- Powerpacks are reusable groups of widgets. Datadog provides preset ones and teams create their own; a change to a Powerpack can be applied to every dashboard that uses it.
- Permissions let you limit which roles, teams or users may edit a dashboard, and version history restores an earlier version if an edit breaks it.
- TV mode is meant for wall displays; scheduled reports send a dashboard as a PDF by email, Slack or Microsoft Teams on a schedule.
- Sharing can be public, invite-only or embedded, with expiry dates, and administrators can switch off the share types they do not allow.
Read more
Datadog dashboards are not a business reporting tool: revenue, stock or HR figures from your business systems belong in the reporting platform you already use. They are viewed in the mobile app but built and edited in the browser. And the data behind them is stored on your Datadog site, outside the Kingdom. Our Datadog page covers the wider platform and what Interkey delivers.
Relatedinfrastructure monitoringapplication performance monitoring
Datadog dashboard templates Interkey sets up
We build a small set of templates rather than dozens of one-off screens, so every service is shown the same way and people learn to read the layout once.
NOC wall screen
One tile per critical service with its health, open alerts and recent changes, sized for TV mode. Red is reserved for conditions with an alert and a runbook behind them.
Read more
Service dashboard
A single layout used for every application: traffic, errors and latency, the slowest endpoints, dependencies, the hosts or containers behind it and deployments overlaid on the graphs. Template variables switch between services and environments; a Powerpack keeps the layout identical everywhere.
Management view
Service targets and their status, availability and incident counts per month, and trends, with a short note under each figure explaining what it means. It can be sent as a scheduled PDF to people who will never log in.
Titles, widget titles and notes are text you write, so they can be in Arabic, English or both. Datadog's own menus and built-in labels stay as Datadog provides them, and we check how Arabic titles display on the screens you will use before rollout. Interkey's engineers work from Riyadh, in Arabic and English, and stay with your team after go-live to adjust dashboards as systems change.
How Interkey sets up monitoring dashboards
-
Name the audiences.
The NOC, the engineering teams and management, with the questions each asks.
-
Check the data.
What is collected today, how it is tagged, and what may leave the Kingdom.
-
Agree definitions.
One way to calculate each figure, and what turns a graph red.
-
Build the templates.
NOC screen, service dashboard and management view, in the languages you choose.
-
Set permissions and sharing.
Who may edit, which share types are allowed, and scheduled reports.
-
Review and hand over.
A review with each audience after a few weeks, then documentation and ongoing support.
Questions teams ask about monitoring dashboards
Can our Datadog dashboards in Saudi Arabia have Arabic titles and notes?
Yes. Dashboard titles, widget titles and notes are text you write, so they can be in Arabic, English or both. Datadog's own menus and built-in labels stay as Datadog provides them. We check how Arabic titles display on your wall screens and laptops before rollout.
Should the operations centre wall screen and the management dashboard be one dashboard?
Usually not. The NOC needs to see in seconds whether anything needs action now; management needs targets and trends over weeks. One dashboard for both tends to be too busy for the first and too technical for the second. They can share the same data and definitions.
Do we pay Datadog for each dashboard we build?
The cost of a dashboard is the data behind it: the hosts, logs, traces and other products Datadog bills for. Building more views on data you already collect is mostly design work. Interkey quotes the Datadog licences and the dashboard set-up together; our pricing guide explains how the bill is calculated.
Can a director or an outside supplier see a dashboard without a Datadog account?
Yes, in several ways: a scheduled PDF report by email, an invite-only link for named addresses, or a public link. Shared links can be given an expiry date, and your administrators can switch off share types they do not allow. Sending reports outside your organisation depends on your Datadog plan.
Is the data shown on our dashboards stored in the Kingdom?
No. Datadog is SaaS, and the data behind its dashboards is stored on your Datadog site; as of November 2026 none is in the Middle East. Sensitive fields are usually masked or dropped inside the Kingdom before data is sent, as agreed with your compliance owner.
How long does it take Interkey to set up dashboard templates for our teams in KSA?
It depends on how many services and audiences there are, how consistently the data is already tagged, and how quickly figures such as availability are agreed. We estimate after a short review of what you collect today, and usually start with the services that matter most.
Next
Related pages
Next step
Plan dashboards for your teams
Tell us who needs to see what: your operations centre, the engineering teams, management. Tell us too what you monitor today and whether titles should be in Arabic. We will suggest a first set of dashboard templates.
Or directly
+966-11-2180999 [email protected]Tawuniya Towers, North Tower, 7th Floor, King Fahad Highway, Olaya, P.O. Box 56835, Riyadh 11564, Saudi Arabia