21–30 of 70 posts
I always liked Datadog as a product but it's also true that it is simply way too expensive if you don't spend significant time cost optimizing. But hosting it myself doesn't really seem like a great solution, I rather invest time in making my app robust than making my monitoring stable.
Earlier quoted context omitted.
I guess I should get into the chat with you, but I meant; you integrate with, let’s say, Jira; there is no jira calling code in the repos, so how does that happen. Bit too in depth for here maybe.
Oh yes! there's no native Jira integration so far - but we have some customers who already integrate oneuptime with Jira. They integrate Jira through workflow webhooks in OneUptime - so when an issue is created in Jira, incident is created in OneUptime and all Status Page subscribers are notified.
I always liked Datadog as a product but it's also true that it is simply way too expensive if you don't spend significant time cost optimizing. But hosting it myself doesn't really seem like a great solution, I rather invest time in making my app robust than making my monitoring stable.
expensive and totally weird pricing structures make it hard to predict costs
Is that all datadog is? I read the horror stories, the monthly bills of 10's of thousands for one server and just assumed there was something more substantial to the product; like they did something groundbreaking or novel. I never cared enough to actually look and see what they did. I use uptime-kuma - https://github.com/louislam/uptime-kuma - it obviously does a fraction of what these other things do but it does ev…
Just about every advertised Datadog alternative does maybe 10% of what Datadog can do, and likely has hundreds less pluggable integrations than Datadog. While it may be the case that it's overkill for a simple application, one of the biggest benefits to Datadog is that there's an integration for just about anything, and the product can go deep if you need it to. The "omg my bill is out of control" issue is usually ma…
Lot of interesting OSS observability products coming out in recent years. One of the more impressive(and curious for many reasons) IMHO is OpenObserve: https://github.com/openobserve/openobserve . As opposed to just a stack, they are implementing just about the whole backend shebang from scratch.
Is that all datadog is? I read the horror stories, the monthly bills of 10's of thousands for one server and just assumed there was something more substantial to the product; like they did something groundbreaking or novel. I never cared enough to actually look and see what they did. I use uptime-kuma - https://github.com/louislam/uptime-kuma - it obviously does a fraction of what these other things do but it does ev…
Just about every advertised Datadog alternative does maybe 10% of what Datadog can do, and likely has hundreds less pluggable integrations than Datadog. While it may be the case that it's overkill for a simple application, one of the biggest benefits to Datadog is that there's an integration for just about anything, and the product can go deep if you need it to. The "omg my bill is out of control" issue is usually ma…
I'd love an open source alternative. But there just isn't one for APM (which is our main use case). Nothing comes close. Every time I see "OpenTelemetry integration" I just close the page. Hours and hours of manual setup, code pushes, etc while New Relic installs once and works.
I assume it's the same for people who use DataDog begrudgingly.
Question for those in the observability space: do moment-in-time observations preserve all of the dimensions of the event, and if so, how do most observability platforms compress the high volume of (ostensibly) low-rank data?
It's "low-rank" until that one day systems start shitting the bed, and you're trying to understand what is going on.
It looks solid and I'd try it if the need arises.
P.S. I am all for OSS.