Summary
The telemetry docs state that usage data "does not include any argument values", but the collected metrics do include some flag values — including the doc's own worked example. Flagging as a small documentation-accuracy fix (this is about the wording, not a concern with the data itself).
Details (at current HEAD)
docs-v2/content/en/docs/resources/telemetry/_index.md:11 (and the docs-v1 copy):
Usage data does not include any argument values or personal information.
But the instrumentation collects flag values:
pkg/skaffold/instrumentation/meter.go AddFlag() records the stringified value of every changed enum flag: meter.EnumFlags[flag.Name] = flag.Value.String(). The same telemetry doc's example JSON shows this: "EnumFlags": {"cache-artifacts": "false", "port-forward": "true"} — those are argument values.AddCliBuildTargetPlatforms() records the raw --platform CLI value (types.go documents it as "the build target platforms specified via command line flag --platform").
Suggestion
Reword line 11 to match reality — e.g. "does not include free-form argument values or personal information; a fixed set of flag values (such as enum flags and --platform) is collected as shown below." I'm happy to open a small docs PR (I'd sign the Google CLA first) if that's welcome. I checked open + closed issues and didn't find an existing report.
Disclosure: I used an AI tool to help spot this; I verified the doc claim against meter.go and the doc's own example JSON myself and take responsibility for it.
Summary
The telemetry docs state that usage data "does not include any argument values", but the collected metrics do include some flag values — including the doc's own worked example. Flagging as a small documentation-accuracy fix (this is about the wording, not a concern with the data itself).
Details (at current HEAD)
docs-v2/content/en/docs/resources/telemetry/_index.md:11(and the docs-v1 copy):But the instrumentation collects flag values:
pkg/skaffold/instrumentation/meter.goAddFlag()records the stringified value of every changed enum flag:meter.EnumFlags[flag.Name] = flag.Value.String(). The same telemetry doc's example JSON shows this:"EnumFlags": {"cache-artifacts": "false", "port-forward": "true"}— those are argument values.AddCliBuildTargetPlatforms()records the raw--platformCLI value (types.godocuments it as "the build target platforms specified via command line flag--platform").Suggestion
Reword line 11 to match reality — e.g. "does not include free-form argument values or personal information; a fixed set of flag values (such as enum flags and
--platform) is collected as shown below." I'm happy to open a small docs PR (I'd sign the Google CLA first) if that's welcome. I checked open + closed issues and didn't find an existing report.Disclosure: I used an AI tool to help spot this; I verified the doc claim against
meter.goand the doc's own example JSON myself and take responsibility for it.