[Heartbeat] User Agent has different case depending on the request

[paulb-elastic]

During the creation of some of our dashboards, we have noticed that the case of the user agent seems to be different depending on the request path.

In some cases it is uppercase Heartbeat and others, lowercase heartbeat. The following list is not expected to be exhaustive, but differences have been observed in the following requests:

• Uppercase Heartbeat (e.g. Elastic-Heartbeat/8.8.0...):
  • GET / (also seen with lowercase)
  • POST /synthetics-*,heartbeat-*/_search
• Lowercase heartbeat (e.g. Elastic-heartbeat/8.8.0…):
  • GET /_license
  • POST /_bulk
  • GET / (also seen with uppercase)

There are cases where GET / is seen with both (from the same version / deployment):

cc @lucabelluccini

[elasticmachine]

Pinging @elastic/uptime (Team:Uptime)

[botelastic[bot]]

Hi! We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

[paulb-elastic]

@graphaelli is this the issue you were referring to (that causes some problems with some of the reporting)?

[graphaelli]

not this one, we work around this with a case insensitive prefix match. The other issue is specific to the synthetics service, tracked in a private issue that I'll ping you on.