I think less techie. I mean, I'm kinda spitballing here about this stuff because my knowledge is only surface level. What I would think would be helpful is something a little more straightforward that just gives me status updates on the major performance logs. This seems like a solution that you still have to configure to tell you what you want updates on.
2
Wow I'd never heard of Telegram before. Seems like a really great solution for a service thats just getting started. I could see it becoming a bit of a nuisance once you reach a certain scale and the events are too frequent.
I've done a couple things with past projects that were useful:
Create some simple database queries that I could view in a dashboard to track user stories (e.g. number of users, number of active users, number of users that have taken X action, etc). Heroku has a nice feature called Dataclips that works great for this.
Simple HTTP application health endpoint. Returns basic system health metrics (e.g. last run time for particular tasks, async task queue depths, etc). If metrics are healthy, the HTTP status returned in 200, unhealthy is 500. Then you can have a simple script pinging the endpoint at some interval, and send an alert when its unhealthy.
1
Jeremy I think you are right, this is a solution for a small-mid services. If I'm going to grow I'll ditch the new account / new user notifications and create a batch notification (like every day/hour) for disabled accounts.
I also have a dashboard (provided by forestapp, great service to create a backoffice in 5 minutes), but the main reason I created this notification engine was that I didn't want to visit any web page as I was doing it too often.
Thanks for the tip about 'health' endpoints. I'll think about it when (and if ) Stori will grow! 🚀
2
interesting
1
Any recommendation on resources that teach how to create and implement bots like yours and Pieter's? (I sorta get the gist of what your code does, but I don't know where to put that code - even if I had someone else write it.)
1
Nice! Notifications about backend do help. I use IFTTT app for these notifications.
@francescomarassi how did you create those graphics on the landing page?
Looks very nice!
Thanks! I created them with my (really limited) knowledge of Sketch. They are based on my real UI, but using only rectangles and circles.
Actually I really like this idea! Telegram bots are quite simple to put together too. Might have to add this to my ops backlog!
Awesome man! Can we use this @jeffdh5 ?
yeah totally, thanks! some variation of it
I didn't think bootstrap a telegram bot could be that simple.
Great idea, btw!
I didn't know you could do that with Telegram. Thanks for sharing.
Congratulations, an intelligent use of Telegram bots (which are very well designed, by the way).
Thanks! Yes, the Telegram API are pretty straightforward and easy to use. The congratulations should go to them :)
Dude there’s a business here.
As a non-techie, I really want this but need something plug and play.
You might like this too https://replain.cc/
Some weeks ago I found https://popcornnotify.com/ that is like this solution but for emails and SMS.
Do you want something like this or less techie?
I think less techie. I mean, I'm kinda spitballing here about this stuff because my knowledge is only surface level. What I would think would be helpful is something a little more straightforward that just gives me status updates on the major performance logs. This seems like a solution that you still have to configure to tell you what you want updates on.
Wow I'd never heard of Telegram before. Seems like a really great solution for a service thats just getting started. I could see it becoming a bit of a nuisance once you reach a certain scale and the events are too frequent.
I've done a couple things with past projects that were useful:
Create some simple database queries that I could view in a dashboard to track user stories (e.g. number of users, number of active users, number of users that have taken X action, etc). Heroku has a nice feature called Dataclips that works great for this.
Simple HTTP application health endpoint. Returns basic system health metrics (e.g. last run time for particular tasks, async task queue depths, etc). If metrics are healthy, the HTTP status returned in 200, unhealthy is 500. Then you can have a simple script pinging the endpoint at some interval, and send an alert when its unhealthy.
Jeremy I think you are right, this is a solution for a small-mid services. If I'm going to grow I'll ditch the new account / new user notifications and create a batch notification (like every day/hour) for disabled accounts.
I also have a dashboard (provided by forestapp, great service to create a backoffice in 5 minutes), but the main reason I created this notification engine was that I didn't want to visit any web page as I was doing it too often.
Thanks for the tip about 'health' endpoints. I'll think about it when (and if ) Stori will grow! 🚀
interesting
Any recommendation on resources that teach how to create and implement bots like yours and Pieter's? (I sorta get the gist of what your code does, but I don't know where to put that code - even if I had someone else write it.)
Nice! Notifications about backend do help. I use IFTTT app for these notifications.
Love that.