Robert May

Just to add to this, the `json` gem isn't even internally consistent: #### Arrays ``` [ ] ``` #### Objects ``` { } ```

Thanks @ohler55! Yeah I think I need a drink after discovering that :sweat_smile: I've been writing our own JSON wrapper to help with old legacy expectations like specs needing that...

I was using master branch at the time I submitted the issue.

Bleh, I can confirm that this is still an issue on Ubuntu. I'm working on exposing the services via the load balancers instead because the workarounds don't work for me...

I just found this issue and I still do not understand why it isn't a supported feature. Not namespacing the metrics is directly against the [Prometheus conventions](https://prometheus.io/docs/practices/naming/#metric-names) for naming metrics....

If anyone else finds this issue looking for an actual solution, put the following in your job config in `prometheus.yml`: ```yaml metric_relabel_configs: - source_labels: [__name__] regex: '(.*)' replacement: 'snmp_${1}' target_label:...

Could it just be a configurable option? I guess it's not especially difficult to use the relabel config above, but having something simple like `prefix_metrics: true` might make it more...

Thanks both! Doh I thought I was getting the body :sweat_smile: I'll try to reread the code and look at where the body is being sent. I was originally hoping...

Aah interesting, thanks! That'll be interesting to see whether passing the whole body to the writer would be faster than iterating it :thinking: I did find that we can't mix...

At GitLab some of our response bodies are...quite large, I suspect :sweat_smile: I was really just trying to experiment with `writev` support in the full Ruby stack as it's something...