Hamilton Turner

Also, a second concern - what should the exported metrics be named? node_exporter moved to using the pattern `node_memory_Capname_metric` (see screenshot from one of my prometheus consoles). I could not...

That's very helpful, thanks. We should export distinct metrics then. @povilasv to answer the second question (what should we export) maybe we just expose the same metrics that node_exporter does,...

Retitled as WIP while I work through the feedback

Thanks! Yes, I actually have some nice commits to push, been busy with my day job. I'll try to get out an update this week On Wed, Apr 29, 2020,...

Well unfortunately real life jumped up and took hold, but I am thrilled to hear that some folks found it useful At this point.... If anyone has time to wrap...

@soulgalore In case you don't know about it, here is one "hacky" way to overcome this. Naturally, if anyone knows a method that relies solely on the ruby that's preferred...

Huh, found an unexpected solution. Doing this causes the provision to happen as the user setup using `override.ssh.username` ``` $ vagrant up --provider digital_ocean --no-provision $ vagrant provision ```

+1. Here's a workaround that provisions with the value of `config.ssh.username` ``` $ vagrant up --provider digital_ocean --no-provision $ vagrant provision ``` Just for kicks, I had my provision script...

I've got parent/child linkage working, what I'm hoping to also have is a top-level "span" (or span-like?) that encompasses the entire flow, so I can easily see the end-to-end latency...

> Yes I'm having trouble with this metric as well. Mine shows two nodes with same id and label and metrics are quite messy This might be an 'oops' in...