talboren

Inspirational stuff here Konstantin! Happy that I have the chance to take part in it!

so what I tried to do is to make it somewhat expensive to do that, by limiting by IPs and fingerprints - so it will be harder ("more expensive") from just getting unique views

https://x.com/elonmusk/status/1863365002109108655?s=48&t=r-0... :D

actually alert fatigue started from healthcare initially where doctors become desensitized to safety alerts, and as a result ignore or fail to respond appropriately to such warnings - it is the same problem in tech companies where you get all these muted Slack channels. It’s a problem almost every company faces at some point of its life

one of our goals is to help you better manage those alerts and reduce the total number. I would have loved to hear more about those 500 alerts use case, im sure checking up Keep would be a super interested use case

are you referring to the product or the toggle in our marketing website?

thanks for the clarification, sorry if it sounded like we’re thinking your comment is not legitimate. It absolutely makes sense.

providers are usually driven by the community! happy to collaborate on that provider if you’d like.

actually, it’s 100 workflows, 20 providers and 10 users. important to note that it’s per deduplicated alert and not every event ingested by keep. what got you surprised about this pricing model?

trying to keep that high pace!

haha! gotta fix those for my ocd: https://github.com/keephq/keep/pull/2684 ^^'

thank you for that! fixed in https://github.com/keephq/keep/issues/2681

it's definitely relevant for early-stage products who deeply care about realiability. are you already handling some amount of alerts today? there's a bunch of stuff you can do with workflows to automate processes and help your users.

we do integrate with AWS Cloudwatch but not yet with Vercel's observability, but can add that if you want to give it try

How does this differ from Traceloop’s Openllmetry? https://github.com/traceloop/openllmetry

check out the "Choose an open source license" website [1]

[1] https://choosealicense.com/

i assumed it's due to bc but does that mean that bc > security? question is how hard do they push/expose the risks of using soon-to-be deprecated tech

why just now? there are many known attacks (SSRF[1] for example) that are based on IMDSv1. maybe i'm missing something but feels like this should have been done a long ago?

[1] https://www.cyberbit.com/uncategorized/aws-imds-v2-secures-s...

companies often find themselves using more than 1 tool that generates alerts, for instance when Datadog is not sufficient (lacking some integration, need some other dashboard capability, etc.).

Grafana Observability survey mentioned that 52% of companies who answered the survey use more than 6(!) different observability tools.[1]

let's leave the fact that Datadog itself expensive as hell and the fact that organizations do move towards consolidations with observability-it's never enough alone.

[1] https://grafana.com/observability-survey-2023/

Paul Ganssle released a great article[1] explaining why you shouldn't use utcnow in 2019.

[1] https://blog.ganssle.io/articles/2019/11/utcnow.html

gonna give it a try today, been wondering how come i never came across anything like that actually (been using the different clients tools)

st2 reminds me a lot of what we're building at https://github.com/keephq/keep (i maintain this oss), there are a few concepts that i really love but the video in the repo really gives me a 90s feelin'

i can't really seem to understand, there's an "enterprise" (with ldap, etc.) version but couldn't find any pricing info

edit: well it's not focused on alerting but alerting is somewhat kinda "event driven"

they surely doesn't help with the "migration" (application layer) part but they help you manage things with code, which is better than nothing (you can do some heavy-lifting to make it work in another provider afterwards)

that's the reason terraform is not really a solution for what I speak about in the blog post.

is things such as alerts/dashboards/proprietary data is easily exportable with SigNoz? For instance if I’d like to manage them with terraform

Like other things around, there’s always the people’s problem but when vendor locked, that’s yet another big issue to address

Was and still is one of the biggest problems orgz have without even knowing they have them. until it hits. I think architects should give that thought from a very early stage of a company and often don’t

YAWS - yet another web server

tough one. can’t say how much i don’t envy him as a founder. stay lean, stay humble, appreciate the honesty and feeling bad for folks who got the message

Wow this is fun.

"open source visual editor" doesn't really comply with "The self-hosted drag and drop editor for React."

looks awesome, a small screenshot in your readme would have helped understand that it's more of a drag and drop component