You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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.
The Commit where we replaced the healthcheck logic:
a5eee90
The text was updated successfully, but these errors were encountered: