Understanding /systemalive service logic

[Alexander_Prikhodko]

I came to know that any AEM instance provides a web service with /systemalive path which responds with a JSON object like this:

{
  "systemStatus": "GREEN", 
  "checks": [
    { "check": "Framework Start Ready Check", "status": "GREEN", "details": "Framework started. Start level: 30; Target start level: 20; Framework state: 32" },
    { "check": "Services Check", "status": "GREEN", "details": "" }
  ]
}

However, I could not find documentation on what exactly the response fields mean and what the logic of their calculation is. Could someone describe it or share a link?

[DEBAL_DAS]

Kindly check the following link: https://medium.com/vrt-digital-studio/13-steps-to-rock-stable-aem-package-installs-d9bbba1f7b15. I will explore it also.

Thanks

[Alexander_Prikhodko]

@DEBAL_DAS Thanks for the materials.

They describe how to configure this service. What about details of what it does? I'm mostly interested in two things:

• what exactly "GREEN" status means (is it e.g. the status of some specific bundle or component?)
• what "Framework started" means (the same question, does it mean that some specific bundle(s) or (component(s) have started?)

[Jörg_Hoh · Accepted solution]

I don't think that this is provided by "any" AEM instance; I only know of AEM CS. Do you see this also on AEM 6.5?

It's correct, there is no documentation for it on AEM side. I would expect to have more documentation on the Apache Felix website...

Anyway, the actual content of this response isn't that important, it is rather the HTTP statuscode. This servlet is normally used to detect the status of the AEM instance. You can check https://adapt.to/content/dam/adaptto/production/presentations/2018/adaptTo2018-System-Ready-framewor... as a starter