jhaygood86

PeachPDF maintainer here --

Would you be able to send your testing corpus to us via GitHub? Or privately?

We've done A LOT of optimizations in the latest versions, including reducing allocations by up to 96% on some documents.

There are a lot of big players in the observability platform world. DataDog comes to mind, and they are EXPENSIVE. I've seen DataDog bills that cost more than the infrastructure they are monitoring! There are some other vendors in the space to, such as Dynatrace, Elastic APM, etc..

They all share a few things in common: They are essentially either silo'ed stores locked behind some vendor system with ever increasing bills, or they require a lot of resources to operate yourself

However, for your average small SaaS business not receiving millions of hits a day, that's all overkill. You just want something to view your logs, some distributed traces connected to those logs, and important system metrics. And you don't want to pay a lot of money to do it either, and even better if you can just run it on the infrastructure you already have and pay for.

That's where PeachTrace comes in. It's an OpenTelemetry-native observability stack that is designed to be self-hosted. There's only a handful of components that need to be installed and set up: You need Windows or some sort of modern Linux, SQL Server 2025+ (the free Express Edition is fine, though there's data storage limits), and you need to set up 3 components: the collector that implements the OTel API that your code talks to, the API layer that the UI and your AI tools can talk to (there's an MCP connector in development as well), and a static HTML/JavaScript dashboard (built in Angular) that talks to the API.

We are starting a limited beta program to work out the kinks in mass distribution of the software. Some known pain points we plan on addresing is building official Docker images, including an "all-in-one" image. We'd also love ideas to improve the software in other ways to make it a more useful product over all.

We dogfood it ourselves already, deployed to a Fedora 44 server (no Docker), with Apache proxying the collector and API, and directly serving the dashboard UI, and a SQL Server Express database instance directly on Fedora. Claude is already a master of using it to investigate and fix bugs in our other applications and client applications we manage!

Many people want the build to be in Docker to.

I personally don't -- I publish on the host build agent and just Dockerize the publish directory

I'd like to point out elemenatary OS as a counter-example:

They have consistently provided a high level SDK for their OS. With elementary OS 6, they moved their high level SDK to using flatpak (not flathub) as a distribution mechanism.

The apps that are "broken" are apps that are not "Flatpak native", so assume they have full write access to ~

Flatpak aware apps (like the ones I develop, or any on elementary OS since flatpak is the native packaging format there) tend to just work.

I live in a "large city" (suburbs in a top 10 metro in the US) and $800k gets you a mansion here still. My 3400 sq ft house is worth ~$350k for a "almost new build" (I had it built in 2015) 6 bed / 4 bath, gigabit fiber, swimming pool / soccer field in the community, great schools, shopping, etc..

I'm also a Principal SWE and my salary is well below $200k, though there are years with bonuses, etc.. that I reach $200k