1. Registering and configuring your personal account

Hello! I want to show you how to use the site https://www.netdata.cloud, you can configure alarm notifications about uncorrected node operation. In my case, I will configure sending notifications in telegram. So, go to the site and create an account.

First of all, let’s install it on the server. Push “enter” and “yes” every time you are asked to do so during the installation process.

If you see this after installation — you are good!

So, we’re almost done! (no :-D)

Go into your account at www.netdata.cloud and get claiming command:

Copy and paste this command into the terminal. And you will see your node in netdata:

2. Set up a telegram bot

  • Go to @BotFather and create a new bot and name it. You will get an API key that looks like: AAAA:BBBBBBBBBBBBBBBBBBB

I create t.me/keepwatcherbot

  • Create group chat and invite your bot you just created and another one: @myidbot. My group: https://t.me/keep_bot_chat You can see alarms there.
  • Write /getgroupid@myidbot and you will get ID of your new created group:
  • Send test message to group via the bot using a bash command :

Don’t forget to replace “AAAA:BBBBBBBBBBBBBBBBBBB” and “-XXXXXX” with you bot’s API key and groupid, which you received earlier.

If you did everything correctly, you will see the text in Your chat:

3. Server setting

  • Run /etc/netdata/edit-config health_alarm_notify.conf
  • Find TELEGRAM_BOT_TOKEN=”” and put there your API key. (remember? it’s like “AAAA:BBBBBBBBBBBBBBBBBBB”)
  • Find DEFAULT_RECIPIENT_TELEGRAM=”” and paste there your group id “-XXXXXX”
  • Save changes & Restart netdata: systemctl restart netdata
  • Let’s test it! /usr/libexec/netdata/plugins.d/alarm-notify.sh test

After that you’ll receive messages to your chat with bot:

Now I will set low system settings to check if the bot is working correctly

Take a look here:

I’ll put $WARNING range from 1 to 5 % usage and $CRITICAL from 5 to 10, % usage, like this:

Also I’ll correct CPU alarms:

I’ll put $WARNING range from 1 to 3 and $CRITICAL from 3 to 10

And finally I’ll correct disk parameters:

I put $WARNING from 1 to 5 and CRITICAL from 5 to 15

Save changes and restart netdata!

After few seconds we received information about critical RAM usage and some troubles with our disk space:

But don’t worry! Since I specifically set low indicators for notifications, our performance is not threatened. However, you can set any parameters that you consider worthy of your attention.

You can configure alerts to match your requests by further reading the netdata documentation:

- https://learn.netdata.cloud/docs/agent/health/quickstart
- https://learn.netdata.cloud/docs/agent/health/reference
- https://learn.netdata.cloud/docs/agent/health
- https://learn.netdata.cloud/docs/agent/daemon/config#health-section-options
- https://github.com/netdata/netdata/blob/master/docs/guides/monitor/dimension-templates.md

Blockchain enthusiast