Datadog · Server monitoring
Server monitoring in Saudi Arabia: Windows, Linux and VMware servers with Datadog
Server monitoring tells you, before your users do, that a server is running out of memory, that a Windows service has stopped or that a VMware host is overloaded. Datadog does this with one Agent on each Windows or Linux server, checks for services, processes and IIS, and a vSphere check that reads your vCenter. Interkey is an official Datadog partner in Saudi Arabia: we sell the licences, roll out the Agent across your data centre, design the alerts and support the platform after go-live.
Orientation
At a glance
The page in one table, for the reader who has five minutes.
- What it covers
- Windows Server, Linux, AIX and VMware vSphere servers in your data centre, beside cloud hosts
- How data is collected
- The Datadog Agent on each server; the vSphere check runs in an Agent pointed at vCenter
- What you watch
- System metrics, processes, Windows services, IIS, event logs, vCenter
- Who it is for
- IT operations teams running most systems on their own servers
- How it is billed
- Per host, per month, in Pro and Enterprise tiers (list prices on our Datadog pricing guide)
- Where the data goes
- To your Datadog site; as of November 2026 Datadog lists no site in the Middle East
- What Interkey does
- Licences, server inventory, Agent roll-out, checks and alerts, residency design and technical support from Riyadh
On-prem server monitoring, in one view with the cloud
In many Saudi organisations the core systems still run on servers the organisation owns: ERP and finance on Windows Server, business applications on Linux, a VMware cluster underneath both, and web front ends on IIS. When users cannot reach a system, the cause is often a full disk, a stopped service, a dead process or a host with no memory left.
Read more
Our Datadog infrastructure monitoring page covers containers, Kubernetes and cloud services. This page stays with the servers in your data centre and the checks that watch them.
In Datadog each server sits in the same view as everything around it: a slow application can be read against its server, the network path and the database behind it. The Agent runs the same way on a server in Riyadh and on a cloud virtual machine. Network devices and traffic are covered on our Datadog network monitoring page.
RelatedDatadog infrastructure monitoring pageDatadog network monitoring page
Server monitoring tools in Datadog: what is watched on each server
One Agent, different checks. Most of these ship with the Agent itself, so the work is configuration, not new software.
| Server | What Datadog collects | Check or feature |
|---|---|---|
| Linux server | System metrics such as CPU, memory, disk and network; resource use per named process; alerts on the count of running instances | Datadog Agent, Process check, Live Processes |
| Windows Server | System metrics; the state of each Windows service you name; event log channels such as System and Security | Datadog Agent, Windows Service check, Windows Event Log |
| IIS web server | Connections, bytes and requests per site; application pool state, uptime and recycles; whether each site and pool is up | IIS check |
| VMware vSphere | CPU, memory, disk and network for clusters, hosts, datastores and virtual machines; vCenter events | vSphere check |
| AIX | The Agent runs on AIX 7.2 TL5 and later and 7.3 TL1 and later, from Agent 7.85.0 | Datadog Agent for AIX |
Datadog's documentation says the IIS, Windows Service, Windows Event Log and vSphere checks are packaged with the Agent. The Process check watches nothing until you name the processes that matter.
Windows server monitoring: services, IIS and event logs
On Windows, many incidents show up first as a stopped service. The Windows Service check reports each service you name as OK when it is running, CRITICAL when it is stopped and WARNING for any other state. Services are selected by service name, not display name, and matched as regular expressions, so one line can cover a family of services. From Agent 7.41 you can also select by startup type.
Read more
The IIS check sends a status for every site and application pool, CRITICAL when one is down, and collects request and connection metrics per site. IIS log files can be collected once log collection is turned on in the Agent; it is off by default. The Windows Event Log integration brings channels such as System, Application and Security in as events or logs, with filters so only what you need leaves the server. Windows Server 2012 R2 is supported only up to Agent 7.46.0, so older servers need an upgrade plan.
Linux server monitoring: processes and what must be running
Beyond system metrics, two features matter most on Linux servers:
- The Process check collects CPU, memory, I/O and thread counts for the processes you name, matched by exact name or by pattern. A process monitor alerts when the number of running instances falls outside the range you set, which catches a daemon that has died quietly.
- Live Processes lists every process running across your servers, normally at 10-second resolution and at 2 seconds while you watch the page. It is switched on in the Agent's configuration.
The same Agent runs the integrations for software on the server. Databases have their own product, covered on our Datadog database monitoring page.
VMware monitoring through vCenter
The vSphere check is configured once per vCenter and covers the environment that vCenter manages: clusters, hosts, datastores, datacenters and virtual machines, plus the events vCenter records. It runs in a Datadog Agent on a separate host, so nothing is installed on the vCenter appliance, and it signs in with a read-only vCenter user that your VMware team creates.
This gives you the hypervisor's view: which host is short of memory, which datastore is filling, which virtual machine is using the CPU. It does not see inside the guest, so for the services and processes of an important virtual machine, install the Agent in it as well.
Server monitoring in the Kingdom: network path, data and regulation
Three questions come up in most Saudi server monitoring projects; settle them before the first Agent is installed.
- The network path. Each Agent sends its data to Datadog over HTTPS. Servers in a closed zone often have no route to the internet, so the path, for example through a proxy, is agreed with your security team.
- Where the data goes. Datadog is SaaS, and as of November 2026 its documented sites are in the US, Germany, Japan, Australia and the UK, none in the Middle East. Server metrics rarely hold personal data, but event logs and IIS logs can carry user names and addresses, so filter them on the server. Our Datadog data residency guide sets out the options.
- Regulation. The National Cybersecurity Authority (NCA) Essential Cybersecurity Controls include logging and monitoring of systems. Our NCA ECC overview explains them in general terms; the authority's own text is the reference.
Interkey's engineers work from Riyadh, in Arabic and English, within the change windows and approval steps of your data centre.
RelatedDatadog data residency guide
How Interkey rolls out server monitoring
-
Inventory the servers.
Operating systems, VMware clusters, IIS servers, and which server carries which service.
-
Quote the licences.
Datadog hosts by tier, with implementation and technical support.
-
Agree the network path and tags.
How each zone reaches Datadog, and one tagging standard for owner, environment and service.
-
Install the Agent in tranches.
Starting with the servers that matter most, using your deployment tools and your change windows.
-
Configure the checks.
Windows services, processes, IIS sites and vCenter.
-
Build dashboards and alerts.
Alerts that name the server, the service and the first thing to check.
-
Operate or hand over.
Interkey operates the platform from Riyadh, or hands it over with documentation and stays on as technical support.
Questions buyers ask
Which Windows Server and Linux versions can the Datadog Agent monitor?
Agent 7 supports Windows Server 2016, 2019, 2022 and 2025, and 2012 R2 up to Agent 7.46.0. On Linux it supports, among others, Red Hat and CentOS 7.0 and later, Ubuntu 14.04 and later and Debian 8.0 and later.
Do we need an agent on every VMware virtual machine?
Not for the hypervisor view. One Agent pointed at vCenter collects metrics for clusters, hosts, datastores and virtual machines. To see the services and processes inside a virtual machine, install the Agent in that machine too.
Can we be alerted when a Windows service or a Linux process stops?
Yes. The Windows Service check reports a stopped service as CRITICAL, and a process monitor alerts when the number of running instances of a process falls outside the range you set.
How is server monitoring licensed for our servers in Saudi Arabia?
Datadog infrastructure monitoring is billed per host, per month, in Pro and Enterprise tiers. Interkey sells the licences in Saudi Arabia and quotes them with implementation and support.
Does our server data leave the Kingdom?
Yes, what the Agent sends goes to your Datadog site, and as of November 2026 none is in the Middle East. Metrics rarely carry personal data; filter event logs and web logs on the server so that only what you approve is sent.
How long does a server monitoring roll-out take?
It depends on the number of servers, how many network zones need an approved path, and your change windows. We give an estimate after the inventory, and roll out in tranches so the most important servers are watched first.
Next
Read next
Next step
Plan monitoring for your servers
Tell us roughly how many Windows, Linux and VMware servers you run, where they sit, and what you monitor them with today. We can quote the Datadog licences, the roll-out and technical support together.
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