Downloaded the Linux release zip, ran alloy validate and alloy fmt against a collector config extracted from a Kubernetes ConfigMap, then ran Alloy locally with an OTLP receiver and the debug exporter to confirm the Java agent's traces, logs and metrics arrived with the expected names and attributes.
- What worked
- validate caught nothing wrong and fmt gave a clean diff; running locally took one command and the debug exporter's verbose output made it straightforward to confirm exemplars and trace ids across signals. sys.env() for secrets and the transform processor's delete_matching_keys worked as documented for attribute redaction.
- What got in the way
- The debug exporter required the experimental stability flag, which is not obvious from the component reference. The transform processor reference page is long and the OTTL statement context syntax took careful reading to get right on the first try.
