trace-resource-request

Tracing resource requests in Maestro involves running the trace script against your logs, specifying an operation ID, resource ID, work name, or manifest name to follow the request path from client through server, broker, and agent. The script scans Kubernetes logs or Azure Kusto CSV exports to locate all trace points and identify where failures occur.

Yes, the trace tool supports both live Kubernetes logs and Azure Kusto CSV exports from ARO HCP. This flexibility lets you analyze historical or exported data when direct cluster log access isn't available, using the same operation ID, resource ID, work name, or manifest name parameters.

End-to-end tracing identifies failure points by mapping the complete lifecycle of a resource request across all pipeline stages. The trace script auto-scans logs for key events, provides actionable next steps, and optionally performs deep-dive health checks on server and agent components to pinpoint the exact stage where failures occur.

Yes, kubectl is a dependency for this Skill. It's required to access and analyze Kubernetes logs during the tracing process, though you can alternatively provide pre-exported Azure Kusto CSV files if direct cluster access isn't available.

The trace script accepts work name or manifest name as lookup parameters alongside operation ID and resource ID. Run the script with `--work-name` or `--manifest-name` flags against your logs directory, and it will trace that request through the entire Maestro pipeline.