netdata-config-from-requirements

To generate a Netdata OpenTelemetry configuration from customer requirements, you provide the written requirements text to an agent, which extracts an atomic inventory and outputs a YAML config bundle with a verification runbook. It delegates receiver and collector pipeline decisions to sibling skills.

Handling missing or conflicting details in a pre-sales document involves generating an explicit open-questions list manifest. The configuration bundle avoids silent defaults by leaving unresolved knobs commented in the otel.yaml file, ensuring the customer addresses every missing requirement.

A Netdata hand-off config bundle for OpenTelemetry collector pipelines includes a consistent folder deliverable containing YAML artifacts, an open-questions manifest, and a customer-run verification runbook. It also delegates per-language instrumentation handoff to appropriate sibling skills.

You can create Netdata otel.yaml files for pre-sales without direct access to the customer's infrastructure by processing their written requirements document. The generated bundle includes a verify.md runbook that the customer applies on their own systems.

The limitation of automated Netdata config generation from written requirements is that it cannot guess missing values. It delegates receiver, collector, and migration composition to sibling skills, while explicitly outputting an open-questions list for any unresolved requirements to prevent silent configuration defaults.

Netdata requirements-to-config supports OpenTelemetry instrumentation handoff for multiple languages by delegating these specific composition decisions to appropriate sibling skills. This ensures the final config bundle remains synchronized with the correct per-language instrumentation rules.