dt-obs-hosts

Inventory and monitor host, process, and container telemetry across environments.

2|1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/israel-salgado/dt-mcp-server --skill dt-obs-hosts-israel-salgado
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dt-obs-hosts
Source: https://github.com/israel-salgado/dt-mcp-server/tree/main/.agents/skills/dt-obs-hosts
Command: npx skills add https://github.com/israel-salgado/dt-mcp-server --skill dt-obs-hosts-israel-salgado

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Host and process telemetry is scattered across systems, making it hard to see overall infrastructure health. This skill collects and normalizes metrics from hosts, processes, containers, and Kubernetes contexts to provide a single source of truth for health and utilization.

Core Features & Use Cases

  • Discover and inventory hosts, processes, containers, and related metadata across cloud and on-prem environments
  • Monitor resource utilization (CPU, memory, disk, network) and track process lifecycles
  • Correlate health signals across layers to support capacity planning, incident triage, and data quality checks
  • Provide technology inventory visibility and lifecycle status to support governance and compliance
  • Enable proactive remediation by surfacing anomalies and saturation across the stack

Quick Start

Provide a live, global health overview for all hosts and processes by returning current CPU, memory, disk, and network metrics across the environment.

Frequently Asked Questions about dt-obs-hosts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor host and container telemetry across cloud and on-prem environments?

Host and container telemetry monitoring normalizes metrics like CPU, memory, disk, and network across cloud and on-prem environments. It collects and correlates data to provide a single source of truth for infrastructure health and utilization.

What is the best way to correlate Kubernetes and host metrics for incident triage?

Correlating Kubernetes and host metrics for incident triage involves cross-referencing process lifecycles and resource utilization across infrastructure layers. This detects saturation and anomalies to support proactive remediation and cross-layer troubleshooting.

Does this infrastructure monitoring approach work for both capacity planning and compliance governance?

Infrastructure monitoring supports both capacity planning and compliance governance by tracking resource utilization and providing technology inventory visibility. It monitors lifecycle status across hosts, processes, and containers to meet these requirements.

How do I get a global health overview of all hosts and processes?

To get a global health overview of all hosts and processes, the system queries current CPU, memory, disk, and network metrics across the environment. This returns a live, unified view of infrastructure health and utilization.

Can I inventory processes and containers across mixed infrastructure without extra dependencies?

Yes, you can discover and inventory hosts, processes, containers, and related metadata across mixed infrastructure. It normalizes telemetry data into a scalable, queryable data model without requiring external dependencies.

Why does cross-layer troubleshooting require normalized host and process telemetry?

Cross-layer troubleshooting requires normalized host and process telemetry because health signals are scattered across systems. Normalizing this data into a queryable model enables accurate detection of saturation and correlation across infrastructure layers.