Datadog integrations in Saudi Arabia: Oracle, SQL Server, VMware, Teams, ServiceNow and Jira

A Saudi enterprise rarely runs one kind of system. A core application may sit on Oracle or SQL Server in a local data centre, on VMware, next to newer services on Kubernetes and a public cloud. The operations team works in Microsoft Teams, and incidents are recorded in ServiceNow or Jira because audit and change management depend on them.

Oracle. The Datadog Oracle integration runs as a check in the Datadog Agent and connects with a dedicated read-only user, over TCP or TCPS. Datadog documents set-ups for multi-tenant and non-CDB databases, Amazon RDS and Oracle Autonomous Database; on RAC, the Agent is configured for each node.

Datadog SQL Server. The check reads SQL Server's performance counters and covers Always On availability groups, failover cluster instances, log shipping and SQL Agent jobs. Its login needs VIEW SERVER STATE, and a few more grants for some metrics. Datadog notes that some metrics are not emitted on Azure managed databases.

Relateddatabase monitoring page

Many Saudi data centres still run most workloads on VMware. The Datadog vSphere check ships with the Agent and connects to vCenter with a read-only user, so one configuration covers the whole vCenter. It collects resource usage for clusters, hosts and virtual machines, and turns vCenter events into Datadog events.

The hypervisor view says a VM is short of CPU. The Agent inside the VM says which process is using it. Interkey usually starts with vCenter, then installs the Agent on the VMs that carry business applications. Our server monitoring page covers the Agent on Windows and Linux.

Relatedserver monitoring page

Datadog Teams integration. Datadog recommends its app for Microsoft Teams: connect your Microsoft tenant, add the app to the teams that receive alerts, then create handles that monitors notify. Engineers can mute a triggered monitor from Teams, and on supported commercial Datadog sites they can declare and update incidents from Teams. Microsoft Workflows webhooks are the fallback where the app cannot be installed. Datadog says the older Office 365 connectors stop working on 18 May 2026, so handles still built on them need moving.

Relatedincident management page

Where no ready-made integration exists, the Datadog Webhooks integration calls any HTTPS endpoint you configure when a monitor triggers, with a custom payload, custom headers, and Basic or OAuth 2.0 authentication. Datadog retries on its own errors or a 5XX response.

Some teams also want an SMS for the alerts that matter most, sent to people outside the on-call rota, such as a duty manager. Interkey Digital Connect, Interkey's SMS platform, takes transactional alerts through a REST API, with sender identities registered on the Saudi mobile networks. Interkey can design the webhook from Datadog to Digital Connect, decide which monitors use it, and keep the message free of personal data.

Every integration is an access decision. Database users, a vCenter account, a Microsoft tenant connection and a ServiceNow user each need approval from a different owner. Interkey prepares one access sheet per integration, with the grants Datadog documents, so your security team reviews them once.

Monitoring data has its own location question. 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. Database metrics rarely hold personal data; query samples, ticket text and alert messages can. Our Datadog data residency guide sets out the options. Support comes from Interkey's engineers in Riyadh, in Arabic and English.

RelatedDatadog data residency guide

An integration is not billed on its own. What you pay for is what it feeds: the hosts the Agent runs on, the database hosts under Database Monitoring, the logs you index and keep, and products such as Incident Management. Our Datadog pricing guide sets out each unit. Teams, ServiceNow and Jira keep their own licences.

The timeline is an estimate, not a promise. A first database or vCenter check can report within days of access being granted; a full estate with alert routing and ticket sync typically takes a few weeks. The drivers are the number of systems and owners, how fast access is approved, and how much agreement the ticketing rules need.