raypettersen

@david-yu what's the status on this feature?


Also noticed this: ```time="2019-02-28T12:23:37+01:00" level=info msg="Listening on :9108" source="main.go:312" 2019/02/28 17:31:22 http: multiple response.WriteHeader calls 2019/02/28 17:31:35 http: multiple response.WriteHeader calls ``` I've never seen these messages before and I...

The log entries are from the exporter (if I understood the question correctly). They came after about 3 hours of runtime.

If there is enough "evidence", then I suggest removing the release for now. Let me know if I can do anything else for providing more details.

I got mine shipped with 1.5.1 Is anyone working on the problem?

@jayendranarumugam thank you so much for this! Had the exact thing happen to me, ref #1472. Spent 2 days knocking my head against the wall. Question now is, what happened...

No-one has experienced something similar? Currently about half our sites are not using their custom probe, while the rest are. Sites are configured by code, so they are 100% identical...

Yes. The problem occurs when you use default backend in your deployment. The result is a healthcheck going to the appgw default backend. Remove default backend from your deployment and...

How about expanding config to something like this. trivy --config terraform trivy --config nginx I'm personally not a fan of wildcards and generic terms like "iac".