feat(status): add ServiceStatus model for store status details #3242
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@DonnieBLT Sir, could you please review this PR? Previously, we were retrieving those details from the cache, but now we are storing them in the database and fetching them from there as well.
This pull request introduces a new
ServiceStatus
model to track the status of various services and updates thecheck_status
function to use this model for more efficient status checks. Additionally, it includes updates to the status page to display the status of the Slack integration.Changes to status tracking:
ServiceStatus
model to store service status information, including fields fortimestamp
,service_name
,is_operational
,response_time
,details
, andlast_error
. [1] [2]check_status
function to useServiceStatus
for tracking and updating the status of services like memory, Bitcoin RPC, SendGrid API, GitHub API, OpenAI API, database, and Redis. Introducedneeds_refresh
helper function to determine if a status update is needed based on a 24-hour refresh interval.i use this for pass test fix #2972