HNHacker News
TopNewBestAskShowJobs

shahargl

79 karma · joined August 11, 2021

Keep (YC W23)
submissionscomments
shahargl··on Show HN: Keep – GitHub Actions for your monitoring tools
got you, so you would imagine some typescript/python/golang sdk that let you define workflows?
shahargl··on Show HN: Keep – GitHub Actions for your monitoring tools
the "workflows as code" is something we are thinking about too. I guess there are pros and cons for every approach and eventually we would want to support both (but need to start with something)
shahargl··on Show HN: Keep – GitHub Actions for your monitoring tools
let me know how I can help
shahargl··on Show HN: Keep – GitHub Actions for your monitoring tools
I agree with you on that as well. The YAML aspect is somewhat of a 'low-level' concern that you shouldn't have to worry about unless you need something highly customized.

Now, let me reverse the question—what would make you keep the tab open?"

shahargl··on Show HN: Keep – GitHub Actions for your monitoring tools
mic drop
shahargl··on Show HN: Keep – GitHub Actions for your monitoring tools
whats the odds. would be super interesting to talk, are you up for it?
shahargl··on Show HN: Keep – GitHub Actions for your monitoring tools
would "datadog workflow automation alternative" would sounds more reasonable? we did want to do that but people told us no one knows datadog workflow automation.
shahargl··on Show HN: Keep – GitHub Actions for your monitoring tools
And what was the solution? How did you eventually address those issues? While I agree that GitHub Actions has its downsides, it's also widely used and simple to start with, which we thought was a good approach. Would you be more comfortable with 'Zapier for Monitoring' or an alternative to 'Datadog Workflow Automation'?
shahargl··on Show HN: Keep – GitHub Actions for your monitoring tools
yea the original thought was "Datadog Workflow Automation" but too many people told us they don't know it.
shahargl··on Show HN: Keep – GitHub Actions for your monitoring tools
thats definitely something we want people to do, use it for their small annoying manual things. in the end of the day I think this will help Keep become very user friendly.
shahargl··on Show HN: Peeng – like Pingdom, but the other way around and simpler
Peeng (which is now gnip.io, ping in reverse) is now only for cron/onprem monitoring but eventually we want to add it a lot of other features (nested subdomains, dynamic status pages, pings (not reverse)).

If you have any idea what would be make Peeng even more great it'll be cool to hear!

shahargl··on Show HN: Peeng – like Pingdom, but the other way around and simpler
any feature you would want and you don't have?
shahargl··on Show HN: Peeng – like Pingdom, but the other way around and simpler
thanks! <3
shahargl··on Show HN: Peeng – like Pingdom, but the other way around and simpler
you give us an URL to check, we HTTP-ping it and then send the results to another URL?
shahargl··on Show HN: Peeng – like Pingdom, but the other way around and simpler
true. the way we see it is that we will few use cases with very good UX, and the second thing is to build integrations to all other tools. think of status page that is integrated with all of your observability tools + you can add your own checks.
shahargl··on Show HN: Peeng – like Pingdom, but the other way around and simpler
Can you elaborate? You are want it to ping your HTTP server and let you know when no response?
shahargl··on Show HN: Peeng – like Pingdom, but the other way around and simpler
we are open to suggestions
shahargl··on Show HN: Peeng – like Pingdom, but the other way around and simpler
This is the MVP which is not much different except a better UX (we hope). The next version gonna have lot of other things such as nested subdomains and status page per endpoint/subdomain.
shahargl··on Show HN: Peeng – like Pingdom, but the other way around and simpler
Nice catch, we are going to change that!
shahargl··on Show HN: Peeng – like Pingdom, but the other way around and simpler
There are plenty of tools that does heartbeat monitoring. We focused on being - free, fast, and simplest UX possible.

The next things we gonna ship are going to be different though - we are going to add status page + nested subdomains so you'll have x.y.peeng.sh so all devices that reports to x.y.peeng.sh will be aggregated to y.peeng.sh status page.

shahargl··on Show HN: Peeng – like Pingdom, but the other way around and simpler
Hey! I've just removed the restriction on "/" for mobiles, can you refresh? (maybe incognito until cache is refreshed or something)
shahargl··on Show HN: Keep – Create production alerts from plain English
Would be happy to answer any question you have. We know our messaging is far from perfect but we are trying. I posted this “show hn” on my LinkedIn so I feel its legit ^^
shahargl··on Show HN: Keep – Create production alerts from plain English
Amazing! Would be cool to chat and understand how we can help
shahargl··on Show HN: Keep – Create production alerts from plain English
wdym? how will it look like?
shahargl··on Is Y Combinator worth the money? Brutally honest review of W22 batch experience
covid
shahargl··on Show HN: Simple open-source cmd+b interface to OpenAI’s API
Thanks for showing! Will you add also midjourney integration?
shahargl··on Grafana Labs – Observability Survey 2023
Some very interesting insights: - 52% of companies use 6 or more observability tools - 11% of companies use 16 or more observability tools - 70% of organizations have centralized observability

About the future: "We posed an open-ended question about what people were most excited about in this space, and it’s clear respondents are keen to see the market’s continued maturation. Some of the top items cited were continued centralization, improved ease of use, and greater data correlation. Several OSS tools also made the list, including OpenTelemetry and Grafana Loki."

shahargl··on Show HN: Keep – Open-source alerting CLI
will do!
shahargl··on Show HN: Keep – Open-source alerting CLI
Hey @EgeAytin, Shahar here. Not 100% sure I understand your question but:

1. You can keep (pun intended) the actual alert YAMLs wherever you like, the CLI gets the alert as an argument.

2. If by observe you mean a UI where you can see all your alerts, this is something we're currently working on.

3. In the upcoming days we will also release "deployment" options so you can click-to-production with your alerts.

Would love to help more if you're still struggling

shahargl··on Show HN: We are building developer-first open-source CLI for alerting
yea actually I didn't manage to edit the body of the post and since I couldn't delete it (didn't even know you can't delete posts) I just let it die ^^"
← PreviousPage 2 of 3Next →