How to send Email Notification when Graylog journal utilization is high?


(Ahmed Adel) #1

How to send Email Notification in these cases?:

  • GrayLog Journal Utilization is high.
  • specific source producing too much messages.
  • specific server has high CPU utilization.

thanks in advance.


#2

If you want to monitor your graylog server, use a monitoring system.
It can handle all of your needs.


(Ahmed Adel) #3

could you kindly recommend one?


(Daniel) #4

i monitor my graylog with telegraf+influxdb+grafana stack, telegraf pulls metrics from grasylog via REST API, puts it in influxdb and grafana does the job of visualizing and alerting, there are a lot of pre-made dashboards for grafana, including graylog ones, mine looks like this:


you can set alerts per graph, there are various notification channels available:
image
i use telegram and email


(Tess) #5

That’s assuming that your company/environment does not already have a monitoring tool. Most corporate environment usually already have these (Nagios, HP OMI, Tivoli, etc etc).

EDIT:
@maniel that screenshot looks dope! I’ll have to take a gander at the stack you described.


#6

+1

You have to choose one what meet with your goals.
We use 6+ monitoring software, in 15+ centralized clusters, because every one has some advantage


(Tess) #7

Dude, I already thought your Graylog setup was nuts. But this takes the cake :smiley:


#8

How would you like monitor 20k+ devices?
We provide services for some million “customers”
Little company little needs, big company…


(Ahmed Adel) #9

thanks for your reply,
i thought it could be done from inside the graylog itself.


#10

not really :frowning:
I suggest to use a monitoring system, because if you also collect performance data, it can help to prevent, or analyze a bottleneck.


(Tess) #11

Mind you, I did not mean “nuts” in a negative sense. In this case “nuts” meant “totally freakin’ awesome:smiley:


(Daniel) #12

also you can monitor other things, for example I’m monitoring a few hosts life parameters (cpu, memory, I/O usage, temperatures etc.), docker and VPN statuses with my TIG stack;-)


(Konrad Merz) #13

It is quite hard to monitor your own system and react on that without generating new problems.
When your system is already under pressure, it cannot waste resources to inform you that is under pressure and with that generating a new set of problems.


(system) #14

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.