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

Adding Lag for PG follower node in status summary command #8054

Merged
merged 7 commits into from
Jul 19, 2023

Conversation

ArvinthC3000
Copy link
Collaborator

@ArvinthC3000 ArvinthC3000 commented Jul 11, 2023

🔩 Description: What code changed, and why?

As an Automate HA user, along with the service status, the user should see follower node lag for Postgresql as well in the cluster status.

Note:
For the leader node, "NA" will be shown

Previously, the cumulative cluster status can be fetched in Bastion by the chef-automate status command. Now the same can be done by the chef-automate status summary command, whereas the chef-automate status will now show the service status(on node level) of each nodes (For reference, PFA in the 'Screenshot' column below)

⛓️ Related Resources

Jira: https://chefio.atlassian.net/browse/CHEF-3561

👍 Definition of Done

👟 How to Build and Test the Change

✅ Checklist

All PRs must tick these:

With occasional exceptions, all PRs from Progress employees must tick these:

  • Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
  • Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
  • Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
  • Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
  • Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

  • Tests added/updated? (all new code needs new tests)
  • Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.

📷 Screenshots, if applicable

image

Demo Video: https://progresssoftware.sharepoint.com/:v:/s/ChefCoreC/EZQhC6ZwjjpCnn3AvV_IZiUBbLHY18dlnnQCVfaR-mea4A?e=0CVU3i

The output of the chef-automate status summary command:

image
continued...
image

Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com>
Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com>
@netlify
Copy link

netlify bot commented Jul 11, 2023

👷 Deploy Preview for chef-automate processing.

Name Link
🔨 Latest commit fae7953
🔍 Latest deploy log https://app.netlify.com/sites/chef-automate/deploys/64b7a3d7712f77000826da01

@ArvinthC3000 ArvinthC3000 changed the title Adding Lag for PG follower node in status summary command [WIP]Adding Lag for PG follower node in status summary command Jul 11, 2023
Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com>
Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com>
@ArvinthC3000 ArvinthC3000 changed the title [WIP]Adding Lag for PG follower node in status summary command Adding Lag for PG follower node in status summary command Jul 18, 2023
@ArvinthC3000 ArvinthC3000 changed the title Adding Lag for PG follower node in status summary command [WIP]Adding Lag for PG follower node in status summary command Jul 18, 2023
Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com>
Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com>
@ArvinthC3000 ArvinthC3000 changed the title [WIP]Adding Lag for PG follower node in status summary command Adding Lag for PG follower node in status summary command Jul 18, 2023
Signed-off-by: Arvinth C <arvinth.chandrasekaran@progress.com>
@sonarqube-for-infrastructure-prod

@vivek-yadav vivek-yadav merged commit 3860995 into main Jul 19, 2023
5 of 7 checks passed
@vivek-yadav vivek-yadav deleted the ar/show_lag_for_pg branch July 19, 2023 09:18
@ArvinthC3000 ArvinthC3000 self-assigned this Sep 4, 2023
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.

None yet

4 participants