It’s nice to see the work by the StarryExpanse people is finally going to see the light of day. It’s going to be a great nostalgia trip for me to play this one.
Also for those who don’t know, TheStarryExpanse was a project to rebuild Riven in 3D with a modern game engine. A few years ago they announced that they were going to collaborate with Cyan before turning over their work to them entirely and moving on.
The key item here is that “combat losses” is what is being tracked. This means KIA as well as Wounded in Action. The actual Russian death count is definitely lower from my understanding but the result is the same. ~300k Russians troops are no longer able to participate in this war.
To add to this I think Russia not too long ago accidentally leaked something close to the actual number deaths. It was around 120k I believe.
What is everyone using for their logging solution? So far I’ve not really done anything and just tail the container log when something is going wrong but a more long term, robust log aggregator would be great....
At work we use the syslog log driver for docker. Essentially any container stdout gets pushed in to the system syslog that then gets ingested into splunk through one of their forwarders. We needed more than just container logs so that’s the reason for that. For a home setup I’d probably do the same but use the ELK stack instead of splunk.
Riven on Steam (store.steampowered.com)
The total combat losses of the enemy from 24.02.2022 to 11.11.2023 (lemmy.world)
mil.gov.ua/…/the-total-combat-losses-of-the-enemy…
Docker logging solution?
What is everyone using for their logging solution? So far I’ve not really done anything and just tail the container log when something is going wrong but a more long term, robust log aggregator would be great....