Tom Judge

Yes this is the JSON exporter, this 'fix' forces the issue but your probably right the real bug is in the json exporter.

I think using should vs must and having a default of error for implementations is a good starting point. However 4xx responses are incredibly gray when it comes to 'is...

> > > > https://github.com/elastic/apm/blob/main/specs/agents/tracing-instrumentation-http.md#outcome > > That spec is used by all Elastic APM Agents, and basically all set client spans with HTTP 4xx to `failure` - that `should`...

> My understanding is this: Some 4xxs are not always errors and in some cases, instrumentation has information about this which could be used to set or not set the...

Can you please provide more details of your deployment and the steps taken to reproduce this issue.

Ok I think we have found the reason here, the name is only resolved when the milter is started here: https://github.com/Cisco-Talos/clamav/blob/main/clamav-milter/connpool.c#L110 We should move resolution to the nc_socket function so...