setting up openshift alert manager mail alerting based on critical and warning

-
Configure alert manager to send mail. This will send mail to 2 diffrent groups
one is managemnet group for ciritical alerts only and second is default group for all alerts.

$  oc project openshift-monitoring

The secret file where alertmanager.yaml content ( encoded in base64 ) will remain is alertmanager-main

convert the yaml content into base64 first
$  cat alertmanager.yaml | base64 -w0

copy value
now edit secret

$ oc edit secret alertmanager-main

find value starts with
alertmanager.yaml:

replace all base64 content from your own . save and exit

now in order to take this secret in effect we must bounce the pod

$  oc delete po -l alertmanager=main

check if all pod came online

$  oc get po -l alertmanager=main

done!

alertmanager.yaml content

resolve_timeout: 5m
route:
group_wait: 30s
group_interval: 5m
repeat_interval: 12h
receiver: default
routes:
- match:
alertname: DeadMansSwitch
repeat_interval: 5m
receiver: deadmansswitch
- match:
severity: critical
receiver: itops
receivers:
- name: default
email_configs:
- send_resolved: true
# Whether or not to notify about resolved alerts.
# The email address to send notifications to.
to: [email protected]
# The sender address.
from: [email protected]
# The SMTP host through which emails are sent.
smarthost: 192.168.1.5:25
# The hostname to identify to the SMTP server.
hello: localmail.mevijay.com
# The SMTP TLS requirement.
require_tls: false
- name: itops
email_configs:
- send_resolved: true
# Whether or not to notify about resolved alerts.
# The email address to send notifications to.
to: [email protected]
# The sender address.
from: [email protected]
# The SMTP host through which emails are sent.
smarthost: 192.168.1.5:25
# The hostname to identify to the SMTP server.
hello: localmail.mevijay.com
# The SMTP TLS requirement.
require_tls: false
- name: deadmansswitch
global:


--note change value of your mail server and from mailid  and to mail id


































Comments











Post a Comment



















Popular posts from this blog









Running cockpit behind nginx reverse proxy with nginx ssl and cockpit non ssl






-















Domain for web access to cockpit : cockpit.mylab.local   cockpit server ip : 192.168.1.61  nginx server ip   : 192.168.1.65  Linux distro using is Centos 7.6   Login to cockpit server   Create a file  [root@repo ~]# vim /etc/cockpit/cockpit.conf  content will be like   [WebService]  Origins = https://cockpit.mylab.local wss://cockpit.mylab.local  ProtocolHeader = X-Forwarded-Proto  AllowUnencrypted = true   save and restart cockpit   # systemctl restart cockpit   now  login to your nginx webserver and install nginx   # yum install nginx -y   create a new file vim /etc/nginx/conf.d/cockpit.conf   paste content as bellow   server {      listen         80;      listen         443 ssl http2;      server_name    cockpit.mylab.local;      ssl_certificate /etc/ssl/certs/cockpit-selfsigned.crt;      ssl_certifica...








Read more










using libguestfs virt-customize tool to modify qcow2 image and reset root password.






-















 ibguestfs is a C library and a set of tools for accessing and  modifying virtual disk images used in platform virtualization. The tools  can be used for viewing and editing virtual machines managed by libvirt  and files inside VMs, scripting changes to VMs, creating VMs, and much  else beside.   virt-customize is one of them as example.  If you forgot root user password here is how you can modify .   # virsh shutdown debian9-vm1  # virt-customize -a  /var/lib/libvirt/images/debian9-vm1.qcow2 --root-password  password:NewRootUserPasswordHere    not only this but you can edit many more.   The –run-command  option is used to execute any command inside a virtual image file.  1) register with rhel subscription  virt-customize -a rhel-server-7.6.qcow2 --run-command 'subscription-manager attach --pool [subscription-pool]'        Install software or packages-  virt-customize -a rhel-server-7.6.qcow2 --install net-tools    Upload a file into image   virt-customize -a rhel-se...








Read more










Running web ssh client on port 443 /80 with nginx as reverse proxy






-















Package used         : shellinabox , nginx Repository used        : epel-release Linux distro used    : Centos 7.6 nginx reverse proxy server ip : 192.168.1.65 shellinabox web ssh server ip : 192.168.1.111 login to web ssh server first install epel-repo # yum install epel-release -y install shellinabox package # yum -y install shellinabox start and enable shellinaboxd service # systemctl enable shellinaboxd && systemctl start shellinaboxd By default shellinaboxd service starts with ssl port 4200 for us to run this in a reverse proxy environment need to make this as insecure hence the encryption will be done by nginx to end user. edit file /etc/sysconfig/shellinabox  like bellow- USER=shellinabox GROUP=shellinabox CERTDIR=/var/lib/shellinabox PORT=4200 OPTS="--disable-ssl-menu -s /:LOGIN" OPTS="-t -s /:SSH:192.168.1.111" save file exit and restart service # systemctl restart shellinaboxd Now open fire...








Read more