Alex Howle

> `net/http` has no notion of route, so it should be `http.target`, which the spec does mention as a required field. I do agree this attribute should be there for...

Pretty sure this is dead. Shame, really. Needs forking, turning into a Go Module, tagging. Possibly use generics for `Gauge` and `Counter`

Same question for DNS and K8s, to be fair. It _feels_ like the k8s one will cope but I'm unsure. would the DNS one need the "A" record to be...

It's already been merged in

This is happening in 0.60.0, too. Nothing special with the config and is just the collector running as native process. I get lots of "error reading process name for pid...

Now, having added "mute_process_name_error: true" to the config I have "... unknown userid xxxxxx" messages instead, where xxxxxx is a number

Heh. I've traced this all the way through the dependency tree. The underlying "os/user" package is failing a UID lookup by returning an error if the user does not exist...

It would be very useful to resolve this issue. As it stands we don't have viable distributed tracing - just separate Producer and Consumer Spans

Yep - I'm seeing the same problem. How is the magic number of `5` arrived at? The user-provided value `self.config.pexpect_timeout` is available to use

Looking a little deeper at this, it seems that initialisation of the `Runner` ensures that `pexpect.TIMEOUT` and `pexpect.EOF` are automatically added, thus preventing them from raising an exception: https://github.com/ansible/ansible-runner/blob/devel/src/ansible_runner/config/_base.py#L205-206 Should...