Pierre Carrier

Could I set the network interface name instead? If so, how? Also, I'm confused as to why this fails / tries to use non-existent network interfaces?

Switched to: ```yaml server: http_listen_port: 3200 grpc_listen_port: 9095 querier: frontend_worker: frontend_address: xi.xmit.dev:9095 query_frontend: search: duration_slo: 5s trace_by_id: duration_slo: 5s distributor: ring: &1 instance_interface_names: - enp7s0 kvstore: store: etcd etcd: endpoints:...

Ah, now looks like grafana-server tries to connect to :3200 over IPv6 but tempo only listens on IPv4… Does that sound about right?

There might soon be a `-csv` (#42) that outputs a format closer to what you'd like now (name, current token, next token, seconds to next token), but doesn't look super...

@creachadair Would you have any idea how to tackle this? While I ping you, would love to chat one day (tons of means to reach me on https://pcarrier.com).

I'm afraid it'd be more trouble than it's worth to support. White on black doesn't work with every phone, non-square fonts can also cause issues. It's also the sort of...

Personally not a huge fan of adding much to the tool running on your typical server itself, particularly when I assume those formats could change any day whereas an install...

Hey thanks for the suggestion. I'd suggest putting this into a different binary as this would fall a bit too far on the side of "bloat" for the small portable...

Oh nevermind go-keyring does not look like a portability mess, worth exploring. Don't know if I'll have any time to think through what the UX should be or study the...

Can be tested on Debian-based systems with: ``` $ sudo apt-get install musl-tools $ rustup toolchain install --force-non-host stable-x86_64-unknown-linux-musl $ rustup target add x86_64-unknown-linux-musl $ cargo build --release --target x86_64-unknown-linux-musl...