Just replicating /etc/truststore does not solve this. You must copy the hmac/master keys files physically from the filesystem (/crx-quickstart/launchpad/felix/bundle25/data) too to the other instance. So the steps are:1. Replicate /etc/truststore 2. Copy the hmac/master keys files physically from the filesystem ( e.g. /crx-quickstart/launchpad/felix/bundle25/data) to all other publish instances

Just replicating /etc/truststore does not solve this You must copy the hmac/master keys were physically copied from the filesystem (/crx-quickstart/launchpad/felix/bundle25/data) to the other instance.

Anyone facing this issue should note that the "client code" expected in this dialog is actually the org id or the tenant id. For example if your cloud product URL is https://experience.adobe.com/#/@aes1448/target or https://aes1448.experiencecloud.adobe.com/ Then your "client code" is "aes1448" for that dialog. I have tested it works with that value.

This is correct answer. The agent must have this - property = { "name=akamai", "service.ranking:Integer=1001" }

Hi Abhay,There was some embed-dependency issue with the repo that I shared. I have updated the code at - GitHub - vivekanand-mishra/app-insights . Now, It should be running fine and request tracking should work properly with AEM just make sure to provide correct instrumentation key. Can you try out this in your AEM app and confirm back. I am looking for contributions in this repo to make this robust for any future AEM-App Insight Integration. If interested, please share your git user details, I ...

Hi Abhay,I hope you are following this article- Performance monitoring for Java web apps in Azure Application Insights | Microsoft Docs I have not tried this. But I suggest modify your AEM start up script and change this line to include java-agent:if not defined CQ_JVM_OPTS set CQ_JVM_OPTS=-Xmx1024m -XX:MaxPermSize=256M -Djava.awt.headless=true -Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=8080,suspend=n -javaagent:Are you facing any issue while setting up agent?Thanks.

kiranv43511543​ Overlaying of OOTB should be avoided to reduce tech debt to AEM upgrades . Recommended way is to create a separate client lib with just one css as mentioned by arunpatidar26​. Just make sure, the client lib category is same as of the OOTB client lib which you want to change. As long as you follow it, it will work for you. For this case, the correct category is - cq.authoring.editor.core, cq.authoring.editor

Agreed with Arun. Instead of overlaying file, creating a custom clientlib is cleaner approach. That way you would be upgrade safe.

I have created a sample project - GitHub - vivekanand-mishra/app-insights Checkout and deploy in your local and follow the testing instruction on Github page.

Anyone looking for a direction to similar issue can find this link useful to solve this- Experiencing Adobe Experience Manager - Day CQ: AEM 64 - Extend TouchUI Rich Text Editor Table Plugin, Add Summary Field