Ok, to do this we need to standardize and bikeshed the client_ip and user_agent fields, since this is not yet in any official common schema.

Thus far for the two schemas that have needed user_agent, we've put it into the http.request_headers map field. I'd be ok with doing the same here for user agent.

For client_ip...should we put this into meta? @Pchelolo thoughts?

+1 to including UA in http.request_headers field

Hm, actually, we get X-Client-IP as a request header from varnish VCL right now. I guess that will continue to be the case in the ATS world? If so, we can also stick it in the http.request_headers map. @ema can we continue counting on the fact that all requests that go through a Varnish/ATS frontend will have the X-Client-IP request header set?

Oh, we already made a an http.client_ip field for api/request and cirrusearch/request. I guess that's where it goes! Hm. I guess we still have to get it from X-Client-IP though, right?

Change 556484 had a related patch set uploaded (by Ottomata; owner: Ottomata):
[eventgate-wikimedia@master] Set WMF specific event field values if they are not set by client

https://gerrit.wikimedia.org/r/556484

Change 556484 merged by Ottomata:
[eventgate-wikimedia@master] Set WMF specific event field values if they are not set by client

https://gerrit.wikimedia.org/r/556484