zoos-integration-core

Source: ZoosGlobal/zoos-integration-core Visibility: Public This page is automatically synchronized from the repository README. Do not edit this generated file directly.

---

Zoos-integration-core 🚀

Central umbrella repository for all Zoos Global Datadog integrations built for client’s Windows infrastructure. Each subdirectory is a self-contained integration with its own README, setup scripts, and Datadog configuration — this repo exists to organize, link, and provide a single entry point into all of them.

---

❓ The Problem — Why This Exists

As the number of custom Datadog integrations grew — covering everything from network security (Netskope) to identity (ADFS) to clustering (WSFC) to endpoint health (SysTrack) — each one living in its own standalone repo created real coordination overhead:

• No single starting point — Anyone new to the team had no central place to discover which integrations existed, what they monitored, or where to find them.
• Inconsistent discoverability — Each integration repo had its own README with its own structure, but there was nowhere to compare them side by side or understand how they relate to each other as a portfolio.
• Duplicated context — Common requirements (Datadog Agent installation, DogStatsD setup, PowerShell execution policy) were repeated across every individual README, with no shared reference point.
• Unclear ownership and status — Without a central index, it wasn’t obvious at a glance which integrations were production-ready, which were in progress, or who maintained each one.

---

✅ The Solution — What We Built

A lightweight index repository that catalogs every Zoos Global Datadog integration in one place, linking out to each integration’s own dedicated repo for full setup instructions, metrics references, and troubleshooting guides.

This repo intentionally stays thin — it doesn’t duplicate the detailed instructions living in each integration repo. It exists purely to make the full integration portfolio discoverable and consistent.

---

📁 Integrations Catalog

Integration	Repository	What It Monitors
Netskope	netskope	Netskope SASE/ZTNA telemetry — IPsec tunnel HA, NPA user sessions, SSL bypass traffic, URL redirects, and URL policy inventory
SysTrack	systrack	Endpoint health, reboot status, application crashes, and application faults across 77,000+ Windows desktops
TLS Certificate Monitor	datadog-tls-cert-integration	Windows Certificate Store (Personal/Root/CA) inventory, expiry tracking, and TLS version compliance
WSFC Monitor	datadog-wsfc-integration	Windows Server Failover Cluster health — cluster/node state, quorum & witness status, network and NIC-level health
ADFS Monitor	datadog-adfs-integration	ADFS service health, certificate lifecycle (token-signing, RPT/CPT certs), trust inventory, and service account lockout
DNS Monitor	datadog-dns-integration	Windows DNS server health and query/zone monitoring
DHCP Monitor	datadog-dhcp-windows-integration	Windows DHCP server health, scope utilization, and lease monitoring

📌 Each repository above is self-contained: clone it directly for setup scripts, Datadog conf.yaml configs, metrics references, pre-built monitors/dashboards, and troubleshooting guides specific to that integration.

---

🧩 Common Pattern Across Integrations

Every integration in this catalog follows the same general shape, regardless of what it monitors:

Windows-native data source (API, WMI, Cert Store, AD, etc.)
        ↓
  PowerShell / Python collector (stateless, scheduled)
        ↓
  Datadog Agent (file-tail logs or DogStatsD metrics)
        ↓
  Datadog Logs / Metrics → Dashboards → Monitors & Alerts

This consistency means once you understand one integration’s setup pattern, the others follow the same conventions:

• Windows-native, Agent-based — every integration runs directly on the target Windows server using the existing Datadog Agent; no separate ingestion services.
• One-click or scripted setup (setup.ps1) — minimizes manual configuration steps and validates prerequisites before going live.
• Dry-run / manual validation step — every integration supports testing before being placed on a recurring schedule.
• Pre-built Datadog monitors and dashboards — each integration ships with ready-to-use alerting and visualization, not just raw data collection.
• Dedicated troubleshooting section — every integration repo documents its own common failure modes and fixes.

---

✅ Getting Started

1. Find the integration you need in the catalog table above.
2. Open that integration’s repository and follow its own README for prerequisites, setup, and validation steps.
3. Each integration’s README includes its own Production Checklist — use it to confirm a successful deployment before relying on it for alerting.

---

🛡️ Maintained By

Zoos Global — Datadog Premier Partner, building and maintaining custom Datadog integrations for client’s Windows infrastructure.

---