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

Updated checkstate to support healthcheck disabling via file #579

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

Skypex
Copy link

@Skypex Skypex commented Feb 20, 2023

Dear maintainers,

in usual environments that run the checkstate.sh (like Kubernetes) containers are immutable.
That means that you cannot simply inject an env variable into the container without restarting the actual container.

However, due to the nature of Splunk it might be needed to perform some maintenance tasks that require a splunkd stop.
This means you need to restart the container first to add the env variable,do your thing and afterwards you need to restart the container again to remove the env variable. So in this case the healthcheck actually decreases availability.

Therefore I would kindly request to add a file check as well. That way you can disable the healthcheck in a running container temporary by creating the file and with out any additional container restarts.
Indeed the env variable method is also an option - nothing changes there.

Pleas consider merging or let me know if you need any additional changes!

@Skypex Skypex requested a review from a team as a code owner February 20, 2023 19:47
@adityapinglesf
Copy link
Contributor

@dp-42 @Skypex follow up -

  • how can we validate if the new values can be picked up by splunk?
  • can you add some more info about how it helps a specific scenario that can be tested to understand the value of these changes

@Skypex
Copy link
Author

Skypex commented Jan 17, 2024

Hi @adityapinglesf,

what new values? There are no new values, I simply added a check for a specific file. That way you can disable the health check by creating the file.

Some scenarios I could think of:

  • We had some occasions that required us to do a splunk fsck repair and many of those operations require splunkd not run
  • When upgrading ITSI the docs also state to stop Splunk - ITSI Docs
  • I am pretty sure that there are more administrative/maintenance tasks that could benefit from this

Hope that answers your questions and helps evaluating this PR.

@marcispauls
Copy link

yep, could be great feature. currently to debug things if shit hits the fan its close to impossible to debug, try to fix, collect diag.
i'm not sure about those && and also update in docs might be useful also maybe some tests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants