[Metricbeat] kibana_stats.usage.telemetry.opt_in_status missing

[cachedout]

Recently, parity tests have begun to show a failure related the opt_in_status key in the usage field for kibana_stats documents.

I believe this may have been introduced relatively recently, possibly in this PR: elastic/kibana#50015

I had thought that Metricbeat would just collect all usage keys but this suggests that perhaps that is not the case? The purpose of this issue is to investigate and potentially fix this discrepancy.

@ycombinator is this something you might have a moment to investigate?

[ycombinator]

@cachedout I checked the code and the usage field is indeed just passed through by the kibana/stats metricset code:

beats/metricbeat/module/kibana/stats/data_xpack.go

Lines 143 to 148 in db234f5

	// Make usage field passthrough as-is
	usage, ok := data["usage"].(map[string]interface{})
	if !ok {
	return "", "", nil, elastic.MakeErrorForMissingField("usage", elastic.Kibana)
	}
	kibanaStatsFields.Put("usage", usage)

Have you been able to reproduce this failure locally? What is the output of the Kibana Stats API that's called by the metricset (GET /api/stats?extended=true&legacy=true) — does it contain the missing/new field?

[botelastic]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[botelastic]

This issue doesn't have a Team:<team> label.