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

Use AEM Healthcheck URL to verify if Publish is healthy #59

Open
mbloch1986 opened this issue Jan 11, 2021 · 1 comment
Open

Use AEM Healthcheck URL to verify if Publish is healthy #59

mbloch1986 opened this issue Jan 11, 2021 · 1 comment

Comments

@mbloch1986
Copy link
Contributor

When we introduced the new EC2 Tag COMPONENT_INIT_STATUS to identify if the provisioning of the EC2 instance finished successful. We've replaced the existing Publisher healthcheck logic in the orchestrator to use this EC2 tag for verification.

Ideally we should use both to identify if the Publisher is healthy or not.

  • Verify if Provisoining was successful
  • Verify that the AEM is healthy via the AEM Healthcheck URL

The Commit where we replaced the healthcheck logic:
a5eee90

@mbloch1986
Copy link
Contributor Author

On top of verify if the provisioning was successful & the healthcheck returns the response code 200 we should also verify if the replication agent queue on the AEM Author instances are empty via the AEM Healthcheck URL. This will allow us to determine if the replication queue contains items or not.

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

No branches or pull requests

1 participant