civiloid

I came up across that thread, that seems to have some good points both for migrating from Prom and against that.

And as some one who is considering a redesign of a montirong stack for my home lab, I wonder what would be opinion of wider community here?

Especially it would be great to get some opinion from people who did the switch (ideally in Production, but that doesn't matter) and what was good and/or bad about that decision?

Thanks.

Yeah, I have something like 12 karma or so, and the account is newly registered (a few days ago). Unfortunately, HN doesn't seems to provide any workarounds for that.

You can make it work with 2.5GbE and maybe even 10 GbE with some luck. But looking at its current state and price I personally would agree that fiber is more future proof.

There is a more concrete example - in the article I've showed iperf3 output, which gave 23.5 Gbit/s - that is actual data. Raw speed was ~24.9-25. Everything else is overhead in that case.

In my case, init7 defines that "fair use" is 0.5 PB per month. So that is about 40 hours until they start asking questions, I guess :)

I doubt I will be any close to that.

True, in terms of price, duplex is cheaper (though compared to overall router cost that is negligible). In my case, I wanted to be able to swap SFPs if input one dies (for any reason), and it doesn't make a lot of sense to buy different modules for different purposes, even if that would save a bit of money.

There is another difference - if I want to go for field connectors and cut it myself, the Simplex connector would cost about 4.15$, and the Duplex would be 6.16$, which would further increase the price difference.

But thanks for the advice, it is indeed a viable option.

As one of the maintainers of go-graphite stack, I'd really like to know more about what didn't work for Gramnarly. Based on values they've provided I can deduce that it was carbonapi + go-carbon, though I wonder if they've considered migrating to graphite-clickhouse. I understand that now it is too late, but maybe more details would help to fix same problem for other people.

P.S. It is also nice to see that feature that I've added long time ago just to have simpler dev setup for myself (vm-backend support) is actually used by people, even though it required few fixes :) (or to be precise - used at least at some point, it is not very clear if they've migrated to built-in one)