Ollygarden otel collector config decomposition
Skill ollygarden/skills/skills/ollygarden-otel-collector-config-decomposition
Decide and execute plain-file decomposition for OpenTelemetry Collector YAML. Use for "should I split this collector config?", "break up this otelcol YAML", "organize it by signal or team", or "create environment overlays". Leaves simple configs intact and proves warranted splits equivalent after merge. Not for Helm, Kustomize, or Terraform packaging; use otel-collector for component facts and ollygarden-otel-collector-config-validation for behavioral proof.From its SKILL.md
npx -y skills add ollygarden/skills --skill ollygarden-otel-collector-config-decompositionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
4.8 KB, as published. Nobody here has run it
Decompose Collector config only when it pays
OllyGarden's default is restraint: decomposition reduces review and ownership scope, but makes every reader reconstruct the whole. A deliberate no-op is the correct result when indirection costs more than it saves.
Use upstream skills for facts that change independently:
otel-collector— current providers, merge behavior, commands, component keys, and distribution support.ollygarden-otel-collector-config-validation— behavioral proof for a processor or connector.ollygarden-otel-collector-k8s-daemonset— a consumer of this workflow, not its source of truth.
Workflow
- Inspect the monolith, environment variants, ownership, and deployment command. Record the exact Collector distribution and version, feature-gate set, and ordered configuration URIs.
- Count the pressures below. If fewer than two are meaningful, stop without changing files.
- If warranted, choose the split from actual change and ownership boundaries.
- Read
references/mechanics.md, then write the split directly unless the user requested a plan or the workspace is read-only. - Validate and compare the fully resolved monolith and split using
references/verifying.md. Do not call the refactor complete without both checks. - Return the decision report.
Decision gate
Decompose when at least two of these are substantial:
- reviews regularly struggle with a config of hundreds of lines;
- independently changing traces, metrics, or logs pipelines share one file;
- copied environment variants are drifting;
- different teams own ingress, processing, egress, or signal pipelines;
- one independently owned block dominates the file, such as sampling policies or scrape jobs.
Keep one file when it fits on a screen, has one pipeline, one owner, and no environment drift. A single weak signal is not enough. An existing split or a request to split is not itself a pressure; judge the underlying config.
Select the boundary
Read references/strategies.md for layouts and overlay mechanics.
- Independent signal teams → by signal:
common.yamlplus complete signal files. This is the usual default and keeps each pipeline together. - Stage-owning teams → by component: a service/pipeline base plus component-type files.
- Same structure, different values → environment overlays on either layout.
- One large independently owned sub-block → one nested
file:inclusion; do not fragment small blocks.
When several fit, prefer the smallest file set that follows the strongest real boundary. Do not invent an ownership model to justify a pattern.
Non-negotiable preservation rules
- Keep each pipeline's
receivers,processors, andexporterssequence in one file. Under the default merge behavior, later sequences replace earlier ones. Even whenconfmap.enableMergeAppendOptionis enabled, onlyservice.extensionsand pipeline receivers and exporters append; processors still replace, and processor order is behavior. - Define shared components once. Distinct
service.pipelines.<name>map entries may live with their owning signal. - Preserve component IDs, values, provider expressions, extensions, connectors, service telemetry, and pipeline membership unless the user separately authorized a behavior change.
- Treat environment overlays as ordered inputs. Record their order, exact configuration URIs, and feature-gate set.
- Validate the complete ordered source set, never a fragment in isolation.
- Compare fully resolved output from the monolith with fully resolved output from the split under the same pinned Collector and environment. Raw YAML versus resolved YAML is not an equivalence test.
- Structural equality does not prove that an OTTL rule, processor, or connector behaves correctly;
explicitly hand that question to
ollygarden-otel-collector-config-validationin the report.
Decision report
End with:
Decision: <decomposed | left as one file>
Why: <criteria met or absent>
Strategy: <by-signal | by-component | overlays | nested | n/a>
Files: <created/changed files or unchanged>
Verification: <merged validation and resolved-equivalence result, pending reason, or n/a>
What ships with it: 9 files
14.6 KB alongside SKILL.md
evals/
references/
- mechanics.md2.6 KB
- strategies.md2.0 KB
- verifying.md3.1 KB
Gives 0 of the 12 instructions most project setup skills give
Counted across 1,553 of the 3,091 authors here whose files we hold, read 2026-09-06
- Write the configuration filein 36 of 1553
- Create the directory structurein 35 of 1553, across 33 files
- Verify the setupin 31 of 1553, across 28 files
- Run the setup scriptin 30 of 1553, across 29 files
- Pre-determine the required sample sizein 29 of 1553, across 12 files
- Check if the configuration already existsin 29 of 1553
- Document every testin 26 of 1553, across 10 files
- Start with a hypothesisin 26 of 1553, across 11 files
- Ask one question at a timein 22 of 1553
- Test a single variable per testin 21 of 1553, across 9 files
- Read product marketing context before asking questionsin 19 of 1553, across 8 files
- Do not peek and stop earlyin 18 of 1553, across 7 files
Said here and by no other author read
- Inspect the monolith and deployment command
- Count the decomposition pressures
- Stop without changing files if pressures are insufficient
- Choose the split from actual change and ownership boundaries
- Write the split directly unless a plan was requested
- Validate and compare the fully resolved monolith and split
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.