talboren

and your feedback is much appreciated! noted for next time. (i actually did the demo in a rush so it was more just showing a simple usage of the platform)

we'll think about some changes to the README asap!

thanks!

wdym by "Rollup's"? I answered re:stackstorm st2 in another comment:

> i think a few major points would be: 1. we're much more integrated and focused on the tools (and even more specifically on the monitoring tools), we actually integrate with their APIs and not only receive events from. 2. trying to be a lot simpler, modern UI, zero-clicks concepts, etc. 3. they're super cool and we learn a lot from them

i think a few major points would be: 1. we're much more integrated and focused on the tools (and even more specifically on the monitoring tools), we actually integrate with their APIs and not only receive events from. 2. trying to be a lot simpler, modern UI, zero-clicks concepts, etc. 3. they're super cool and we learn a lot from them

well actually documentation around that is still under construction (https://docs.keephq.dev/development/adding-a-new-provider) but adding a new integration (provider in our terms) to Keep is a piece of cake! happy to chat in our Slack (https://slack.keephq.dev) or over a zoom, what ever works for you :)

Datadog or us? ^^'

thanks! happy to help your team migrate to Keep and send out a few complimentary monitors ;)

thanks for the feedback here, that’s really important for us and we actually just refactored the readme a couple of days ago. any concrete action item you’d suggest?

lol

yea, you’re definitely right. we should’ve mentioned something like “GitHub actions but reliable”.

actually our readme mentions datadog workflow automation as a reference though people are less familiar with it

Self hosted version supports both single tenant mode (no users/login at all) or multi tenant mode where you can configure your own auth0 account and work with all of their supported IDPs. It’s not so well documented but I can have that documented ASAP

or is it just to a great distance? (https://www.google.com/search?q=farther&rlz=1C5CHFA_enIL1013...)

surely a good alternative to userflow which kinda sucks

we're now available at https://www.gnip.io (or gnip.app or gnip.dev)

will check that, from mobile? thanks!

wdyt about gnip (reversed ping) as an alternative to peeng?

love that! i think we have a winner

more of the same, isn’t it?

not sure what do you mean, can you explain?

You can send query params when hitting your subdomain. We keep those query params and can then display them to differentiate between requests (coming from a NAT gw) —- does that help?

Thanks @jedberg. I’ll add a few examples to the front page.

re the GitHub repo: it's just a reference to our OSS project "Keep", not the BE of Peeng. sry for the confusion

we liked the .sh domain but perhaps it wasn't the best choice. signing in and creating a subdomain gives a full list of examples: https://snipboard.io/l2TU1c.jpg

let me know if I can help anyhow

Hey jaequery, Peeng is the solution for you! happy to further help you set it up, join our Slack at https://slack.keephq.dev and I'll shoot you a message

Those are the compatibility issues we had and the reason we decided to put a mobile redirect on -- working to fix this ASAP!

It's your configured endpoint that gets POSTed when your Peeng subdomain stops receiving pings.

Anyway, gotcha, we'll do some work on the text there! Thank you!

Yep, got that feedback a couple of times -- we'll do something about it, we plan on supporting more domains anyhow.

Thank you for the feedback!

A more detailed documentation can be found here https://www.keephq.wiki/applications/github :)

Back to biz

Is it time to move back to Jenkins? :X

If it’s completely burned when entering the atmosphere, is it really?

hope that's true ^^'