[All beats] HTTP request should include the beat name and the version as part of the user-agent

[archon810]

This is a follow-up to #10170, but for all beats, not just Heartbeat.

Specifically, Metricbeat in my case (I haven't checked the others).

[elasticmachine]

Pinging @elastic/integrations-services (Team:Services)

[ph]

For the person doing the implementation, its matter of auditing all the HTTP we are using in the beats and add a round tripper to the http client. You could reuse the code in

beats/x-pack/elastic-agent/pkg/kibana/round_trippers.go

Lines 20 to 33 in cfffc58

	type UserAgentRoundTripper struct {
	rt http.RoundTripper
	userAgent string
	}
	// RoundTrip adds a User-Agent string on every request if its not already present.
	func (r *UserAgentRoundTripper) RoundTrip(req *http.Request) (*http.Response, error) {
	const userAgentHeader = "User-Agent"
	if len(req.Header.Get(userAgentHeader)) == 0 {
	req.Header.Set(userAgentHeader, r.userAgent)
	}
	return r.rt.RoundTrip(req)
	}

[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.

[archon810]

Bump.

[wasserman]

It helpful to include the beat's hostname and/or IP in this User-Agent string. I am thinking of scenarios where there is a beat failing to authenticate to the cluster and it is hitting the cloud through a corporate proxy. All beats may appear to come from the same IP, which makes identifying the problem beat challenging. Adding hostname/IP could make it easier for the team that focusing on the Elastic stack in an organization to identify the source host.
This would allow auth or apikey failures to have an audit trail when a load-balancer is logging the User-Agent string. Maybe even available in Elastic logs if this is support and can be switched on log4j.

[elasticmachine]

Pinging @elastic/agent (Team:Agent)