elasticsearch-aws says we are good at invalid host headers

[codefromthecrypt]

was looking into why we drop so much and noticed this..

[anuraaga]

That's very bizarre... Do I see it correctly in that all requests have bad host in the beginning and then that stops?

[codefromthecrypt]

well it was a burst of traffic in wrk. I didn't look carefully or even Google. seems interesting they have a dashboard for this! unless it is a magic dashboard for repeating errors...

…

On Sat, Aug 17, 2019, 7:21 PM Anuraag Agrawal ***@***.***> wrote: That's very bizarre... Do I see it correctly in that all requests have bad host in the beginning and then that stops? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#139?email_source=notifications&email_token=AAAPVV7GV4BK5CRDGD7C5OLQE7NNLA5CNFSM4IMPBHTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4QJHKI#issuecomment-522228649>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAPVV6LIXYYY4Z2GFCTJ2LQE7NNLANCNFSM4IMPBHTA> .

[anuraaga]

Sorry I meant stopped being invalid during the run. I see 5 min where red matches blue, then a calm, then large blue with no red. Was wrk running the entire time or just that five min?

[codefromthecrypt]

oh i don't run wrk 5 minutes.. most is 100 seconds. that was probably me running a couple times

…

On Sat, Aug 17, 2019 at 8:15 PM Anuraag Agrawal ***@***.***> wrote: Sorry I meant stopped being invalid during the run. I see 5 min where red matches blue, then a calm, then large blue with no red. Was wrk running the entire time or just that five min? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#139?email_source=notifications&email_token=AAAPVV7V4THJHDEL42FRFYDQE7TXPA5CNFSM4IMPBHTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4QKANA#issuecomment-522231860>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAPVVY2XSDRP5OLKHYJSYTQE7TXPANCNFSM4IMPBHTA> .