Where to find the log for asset compute workers | AEM Processing Profile | Asset Compute

In Adobe Experience Manager as a cloud service (AEM aa cloud service) when someone use asset compute worker (custom or ootb) via AEM Assets processing profile, a developer has to debug and find the issue when processing is getting fail. In this situation, where a developer will find or access the log for Adobe IO runtime or Asset compute worker, whether in AEM logs or IO runtime logs.

Image 1: Asset processing failed

Finding error

1. First, we need to look the AEM error log file and see if processing is trigger and any error printed in the log file.
   
2. Second, specially for asset compute worker, go to your local machine, open the terminal and get the logs using aio command "aio app logs". After that you will get the log from Adobe IO runtime and one can easily access the log and find the cause of failure.

Image 2: aio logs showing failure message

Note: To access the Adobe IO runtime logs, your machine should have the adobe aio installed. 

References

1. Debug an Asset Compute worker | Adobe Experience Manager

How to preview HTML in VS Code

1. Open VS Code, and go to extension section.

2. Search for "HTML Preview" and select one HTML Preview extension to install.

3. After successful install, open a HTML file in VS code editor. 

4. Right click on the file name from header. Click on option "Open Preview".

This will split your screen and show the preview right side of the screen and code editor left side of the screen.

Enjoy coding!

What is the purpose of go-live checklist?

A project go-live checklist is essential for ensuring a smooth and successful launch of a project, product, or service. Here are the key purposes it serves:

1. Readiness Assessment: It helps evaluate the readiness of the project, ensuring all necessary steps have been completed and everything is in place.
2. Risk Mitigation: By identifying potential issues in advance, it allows teams to address them proactively, reducing the risk of problems during the launch.
3. Quality Assurance: It ensures the completeness and quality of the solution, making sure it meets the required standards before going live.
4. Coordination and Communication: It aligns all team members and stakeholders, ensuring everyone knows their roles and responsibilities during the go-live phase.
5. Smooth Transition: It facilitates a seamless transition from development to operational use, minimizing disruptions and ensuring a successful implementation.