The User-Agent header is set on each request to inform the server about what type of client it is communicating with. In this case, we are not yet setting User-Agent for analytics upload requests yet.
We should do, and it should look something like the following:
User-Agent: AnsibleTower/3.6.0}
LGTM. I fiddled around with sending the analytics manually but could not really introspect into the request, neither do I have access to ingress service so could not really see that either. Do you have any suggestions for testing?
Is this going to get backported to any prior releases?
@kdelee I don't have access to the ingress service either, but we could check to make sure it is in the request header. Though the only real way I can think of to do that is to run the ship() method in something like shell_plus and set a pdb.set_trace() in that section of code, then introspect the request object after it has been created to look at the headers.
@benthomasson Would you be able to look at the header from the automation analytics side?
Got access to logs from ingress service, can confirm that User Agent is getting set from devel instances

Most helpful comment
Got access to logs from ingress service, can confirm that User Agent is getting set from devel instances
