sendgrid-nodejs VS blackbox_exporter

You will need an API key from SendGrid to use this package. You can get one by signing up for a free account at https://sendgrid.com/.

Formspark is a great service for this with a generous free tier. If you end up scaling up and need more and/or advanced transactional emails you may consider an email API like SendGrid, Amazon SES, or Waypoint.

SendGrid. An industry-leading email API with good deliverability and a comprehensive suite of analytics.

Solution: Read on to learn how to build a personal marathon training plan generator Streamlit-hosted app from personal workout data using the Strava API, LangChain agents, chains, few-shot prompt templating, PromptTemplates, OpenAI, and SendGrid. This can also be applied to personal training, nutrition, and more!

Sendgrid, Mailgun, or Postmark are great solutions if you have a need for transactional emails that are technical. I still prefer using Customer.io for this need. If you’re unsure what transactional emails are, check out this guide.

Email is sent via an event. I have a Lambda function triggered off an EventBridge rule in my serverless toolbox that will send an email via SendGrid. This allows me to reuse that functionality across all my projects, once again minimizing the amount of resources I have allocated in the cloud.

SendGrid

You could consider to use some email delivery service like Mailgun or Sendgrid. They offer free tiers and their servers are more accepted than some random self-hosted server.

First let's set up a Sendgrid account. Sendgrid has a free tier that enables 100 free emails a day. So let's sign up at https://sendgrid.com/.

Visit the SendGrid website and sign up for a free account. To create your account, provide the required information, including your email address and password.

https://github.com/prometheus/blackbox_exporter/blob/master/...

So you need 2 modules, one for each ip version. As for autamating setting these up, we deploy our Prometheus server with salt so we can use Jinja templating in all our Prometheus config files. That really cuts down on repeating boiler plate code.

This is also interesting for other reasons; in host downtime situations you can sometime see they will drop one type of traffic and not the other.

A Pi is more than enough to run a full monitoring stack. Why reinvent the wheel?

You can also use the blackbox_exporter to probe various endpoints. But in reality, you don't need to do this most of the time since the up metric gets you what you want.

Synthetic Monitoring is the Grafana Cloud implementation. It uses the blackbox_exporter

Prometheus blackbox_exporter. Free and open source.

Check something called blackboxexporter https://github.com/prometheus/blackbox_exporter

I have seen some people doing with these traditional relational databases, and I was wondering if it could be a good fit for prometheus+grafana as I have been messing around with prometheus BlackBox exporter (https://github.com/prometheus/blackbox_exporter) for web status monitoring.

You should look into the projects https://github.com/prometheus/node_exporter and https://github.com/prometheus/blackbox_exporter

You could use prometheus as a monitoring tool, blackbox_exporter to "export" the urls to prometheus, alertmanager for notifications, and grafana for nice gui dashboards (and maybe also notifications).