For
- https://hub.docker.com/r/prom/alertmanager
Awesome
- https://github.com/samber/awesome-prometheus-alerts
- https://awesome-prometheus-alerts.grep.to/rules
So to add
You alert manager configuration may look something like below:
You should be up & running with this sample configurations.
Spread your love for M2SH :)
#prometheus #prom #alert #alert_manager #docker #dockerfile #slack
prometheus
you can use an alert manager, it has a docker file in the link below:- https://hub.docker.com/r/prom/alertmanager
Awesome
Prometheus
alerts:- https://github.com/samber/awesome-prometheus-alerts
alertmanager
has rules, you can see sample rules here in the following link:- https://awesome-prometheus-alerts.grep.to/rules
So to add
alertmanager
service:alertmanager:
image: prom/alertmanager:latest
restart: always
command: --config.file=/etc/alertmanager/alertmanager.yml
volumes:
- ./alert/config/alertmanager.yml:/etc/alertmanager/alertmanager.yml
dns:
- 8.8.8.8
You alert manager configuration may look something like below:
global:
resolve_timeout: 5m
route:
# When a new group of alerts is created by an incoming alert, wait at
# least 'group_wait' to send the initial notification.
# This way ensures that you get multiple alerts for the same group that start
# firing shortly after another are batched together on the first
# notification.
group_wait: 10s
# When the first notification was sent, wait 'group_interval' to send a betch
# of new alerts that started firing for that group.
group_interval: 5m
# If an alert has successfully been sent, wait 'repeat_interval' to
# resend them.
repeat_interval: 30m
# A default receiver
receiver: "slack"
# All the above attributes are inherited by all child routes and can
# overwritten on each.
routes:
- receiver: "slack"
group_wait: 10s
match_re:
severity: error|warning
continue: true
# - receiver: "sms"
# group_wait: 10s
# match_re:
# severity: error
# continue: true
receivers:
- name: "slack"
slack_configs:
- api_url: 'YOUR-WEBHOOK-URL'
send_resolved: true
channel: 'monitoring'
text: "{{ range .Alerts }}<!channel> {{ .Annotations.summary }}\n{{ .Annotations.description }}\n{{ end }}"
# - name: "sms"
# webhook_config:
# - url: https://a.b.c:8080/send/sms
# send_resolved: true
You should be up & running with this sample configurations.
Spread your love for M2SH :)
#prometheus #prom #alert #alert_manager #docker #dockerfile #slack
GitHub
GitHub - samber/awesome-prometheus-alerts: 🚨 Collection of Prometheus alerting rules
🚨 Collection of Prometheus alerting rules. Contribute to samber/awesome-prometheus-alerts development by creating an account on GitHub.
Create a linux SWAP file:
https://linuxize.com/post/create-a-linux-swap-file/
#linux #swap #swapfile #swappiness #swapon #mkswap
https://linuxize.com/post/create-a-linux-swap-file/
#linux #swap #swapfile #swappiness #swapon #mkswap
Linuxize
Create a Linux Swap File
Swap is a space on a disk that is used when the amount of physical RAM memory is full. When a Linux system runs out of RAM, inactive pages are moved from the RAM to the swap space.
Forwarded from Quera
🔹مسابقاتِ برنامهنویسیِ Backend و Frontend تومن
در این مسابقه سوالاتِ🔹بکاند، Python و Django و 🔹فرانتاند Front-End و Reactjs میباشد.
👈علاقهمندان میتوانند به صورت مجزا در این دو مسابقه شرکت کنند.
🔹همراه با ۳ میلیون جایزه نقدی
☝️از نفرات برتر این مسابقه جهت استخدام در شرکت تومن دعوت به عمل میآید.
⏳زمان مسابقه: ۲۱ تیرماه روز جمعه
ثبتنام از در این مسابقه از طریق:👇
🔹https://quera.ir/r/dpi1h
➖➖➖➖➖➖➖
@Quera_ir
در این مسابقه سوالاتِ🔹بکاند، Python و Django و 🔹فرانتاند Front-End و Reactjs میباشد.
👈علاقهمندان میتوانند به صورت مجزا در این دو مسابقه شرکت کنند.
🔹همراه با ۳ میلیون جایزه نقدی
☝️از نفرات برتر این مسابقه جهت استخدام در شرکت تومن دعوت به عمل میآید.
⏳زمان مسابقه: ۲۱ تیرماه روز جمعه
ثبتنام از در این مسابقه از طریق:👇
🔹https://quera.ir/r/dpi1h
➖➖➖➖➖➖➖
@Quera_ir
Did you know that python
#python #print #sep #separator
print
command takes sep
argument as a separator between string arguments?print('ali', 'reza', sep=', ') # output: ali, reza
#python #print #sep #separator
https://www.thoughtworks.com/insights/blog/rest-api-design-resource-modeling
#RESTAPI #REST #API #collection #resource #CQRS #CRUD #URI #URN #REST_API
#RESTAPI #REST #API #collection #resource #CQRS #CRUD #URI #URN #REST_API
Thoughtworks
REST API Design - Resource Modeling
“The key abstraction of information in REST is a resource. Any information that can be named can be a resource: a document or image, a temporal service (e.g. "today's weather in Los Angeles"), a collection of other resources, a non-virtual object (e.g. a…
https://stackoverflow.com/questions/18770545/why-is-my-git-submodule-head-detached-from-master
#stackoverflow #git #submodule
#stackoverflow #git #submodule
Stack Overflow
Why is my Git Submodule HEAD detached from master?
I am using Git submodules. After pulling changes from server, many times my submodule head gets detached from master branch.
Why does it happen?
I have to always do:
git branch
git checkout mas...
Why does it happen?
I have to always do:
git branch
git checkout mas...
Add health check to
- https://github.com/grpc-ecosystem/grpc-health-probe
#grpc #health #health_check
gRPC
services and use this command line tool to check for service status:- https://github.com/grpc-ecosystem/grpc-health-probe
#grpc #health #health_check
GitHub
GitHub - grpc-ecosystem/grpc-health-probe: A command-line tool to perform health-checks for gRPC applications in Kubernetes and…
A command-line tool to perform health-checks for gRPC applications in Kubernetes and elsewhere - grpc-ecosystem/grpc-health-probe
ghz
:- Simple
gRPC
benchmarking and load testing tool inspired by hey
and grpcurl
.sample
ghz
command to load test a service:ghz --insecure --proto my_proto.proto --call my_proto.AService.MethodById -d '{"user_id": "5d32b19b6fea7a28de186b15"}' 0.0.0.0:9000
The sample output will be:
Summary:
Count: 200
Total: 557.11 ms
Slowest: 319.18 ms
Fastest: 33.30 ms
Average: 132.56 ms
Requests/sec: 358.99
Response time histogram:
33.300 [1] |
61.887 [6] |∎∎
90.475 [98] |∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎
119.062 [23] |∎∎∎∎∎∎∎∎∎
147.650 [12] |∎∎∎∎∎
176.238 [10] |∎∎∎∎
204.825 [7] |∎∎∎
233.413 [12] |∎∎∎∎∎
262.000 [9] |∎∎∎∎
290.588 [9] |∎∎∎∎
319.176 [13] |∎∎∎∎∎
Latency distribution:
10% in 70.25 ms
25% in 83.84 ms
50% in 89.90 ms
75% in 178.51 ms
90% in 275.84 ms
95% in 301.41 ms
99% in 317.01 ms
Status code distribution:
[OK] 200 responses
#grpc #loadtest #ghz #grpcurl #hey #proto