Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CheckMK Create a Redis Check #5770

Open
1 of 5 tasks
kayiwa opened this issue Jan 21, 2025 · 1 comment
Open
1 of 5 tasks

CheckMK Create a Redis Check #5770

kayiwa opened this issue Jan 21, 2025 · 1 comment
Assignees
Labels
Operations pulls issues into the Operations ZenHub board

Comments

@kayiwa
Copy link
Member

kayiwa commented Jan 21, 2025

What maintenance needs to be done?

Create a redis check for all instances that run it. CheckMK has pretty good MySQL documentation. That can be used in conjunction with this link

Level of urgency

  • High
  • Moderate
  • Low

Why is this maintenance needed?

This would allow us to know about any redis outages pretty early

Acceptance criteria

  • Checkmk says "OK" when the connection is good
  • Checkmk says "WARN" or "CRIT" when the connection is bad (for example if it is not running)

Implementation notes, if any

@aruiz1789 aruiz1789 added the Operations pulls issues into the Operations ZenHub board label Jan 23, 2025
@aruiz1789
Copy link
Contributor

Created a Service Check for Redis and explicitly assigned it to figgy-web-stagin1.
Stopped the service and confirmed the slack alert and recovery.

Service PROBLEM notification
Host: figgy-web-staging1 (IP: 128.112.204.177)
Service: Redis Service (TCP 6379)
State: CRITICAL
Additional Info
connect to address 128.112.204.177 and port 6379: Connection refused
Please take a look: @ansible
Check_MK notification: Wed Jan 29 13:53:36 EST 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Operations pulls issues into the Operations ZenHub board
Projects
None yet
Development

No branches or pull requests

2 participants