Our great sponsors
-
self-hosted
Sentry, feature-complete and packaged up for low-volume deployments and proofs-of-concept
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
First, are they in a competition to see if they can use every technology known to humanity? Unless those things never require any maintenance or debugging or blowing out disks, the more moving parts the more the risk of the error capture system needing an error capture system
Second, and closely related to the first, I'm a kubernetes shop, so I'd have to port, and then maintain, their compose file over to a k8s setup, taking responsibility for understanding which parts I can horizontally scale vs not. Compare to the old way: RMQ (bleh, but fine lots of people use it), PG, and one container. I was still responsible for making the Deployment for it, but one versus "tens" of them matters
Good, tell them to fix their fucking agent to stop spamming my logs with their python backtrace. I mean, seriously, who logs a backtrace for a simple connection refused when it's going to poll that endpoint every minute or whatever?