{"id":57141,"date":"2023-04-21T13:10:42","date_gmt":"2023-04-21T07:40:42","guid":{"rendered":"https:\/\/www.tothenew.com\/blog\/?p=57141"},"modified":"2024-06-10T15:39:00","modified_gmt":"2024-06-10T10:09:00","slug":"aem-replication-queue-monitoring-using-aws-cloudwatch","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/aem-replication-queue-monitoring-using-aws-cloudwatch\/","title":{"rendered":"AEM Replication queue monitoring using AWS CloudWatch"},"content":{"rendered":"

This post will explain the approach to monitor the Replication Queues of Adobe Experience Manager (AEM) using AWS CloudWatch logs.<\/span><\/h3>\n

Issue:<\/b><\/p>\n

    \n
  1. The AEM content replication appears to be blocked.<\/span><\/li>\n
  2. Editors can create content, but the activated pages on the CQ5 publish instance are not updated.<\/span><\/li>\n<\/ol>\n

    Replication issues will occur with the following scenarios:<\/span><\/p>\n

      \n
    1. The publisher instance is not accessible<\/span><\/li>\n
    2. Author to Publisher connectivity is missing<\/span><\/li>\n
    3. Bulk activation of pages or DAM assets<\/span><\/li>\n
    4. Authentication and authorization issue due to credentials mismatch.<\/span><\/li>\n
    5. DNS misconfigurations in the Transport section.<\/span><\/li>\n
    6. Transport users not having to write permission for the replicated content on the target instance<\/span><\/li>\n
    7. Conflicts when writing content to the oak repository (MongoDB repository)<\/span><\/li>\n
    8. Network issues<\/span><\/li>\n<\/ol>\n

      In case there isn\u2019t any monitoring in place, usually, the customer notifies the AEM Support team whenever there is an activation issue or the activated contents are not updated in the publisher instance. We recommend ensuring that replication queue monitoring is enabled because Ops Team\/Support team will be notified if a page or DAM asset becomes stuck in the replication queue.<\/span><\/p>\n

      In this blog, we will explain one of the methods for monitoring the replication queue –\u00a0 CloudWatch logs. Using this monitoring method, the appropriate team will be notified if there are any issues in the replication queue.\u00a0<\/span><\/p>\n

      Here are the 5 steps to implement the replication Queue Monitoring using Cloudwatch:<\/strong><\/p>\n

        \n
      1. Create a replication logger in the AEM instance.<\/span><\/li>\n
      2. Install and Configure the Cloudwatch logger in the AEM instance.<\/span><\/li>\n
      3. Create an SNS Topic.<\/span><\/li>\n
      4. Setup the Cloudwatch replication logger.<\/span><\/li>\n
      5. Configure Notification details in the AWS SNS.\u00a0<\/span><\/li>\n<\/ol>\n

        Step:1\u00a0 Create a replication logger in the AEM instance<\/b><\/h4>\n

        Navigate to OSGI console -> Configuration tab<\/span><\/p>\n

          \n
        1. Search logger for Apache Sling Logging Logger Configuration.<\/span><\/li>\n
        2. Name of the Log file: replication.log<\/span><\/li>\n
        3. Message pattern: same<\/span><\/li>\n
        4. Logger: <\/span>com.day.cq.replication<\/span><\/li>\n
        5. Save the configuration.<\/span><\/li>\n<\/ol>\n

          Step:2\u00a0 <\/b>Install and Configure Cloudwatch logger in AEM instance<\/b><\/h4>\n

          1. Login to the AEM author instance for which we want to set up cloudWatch monitoring.<\/span><\/p>\n

          2. Run the following commands:<\/span><\/p>\n

          sudo yum install awslogs<\/span><\/pre>\n
          3. Configure the awslogs.conf file to pass the logs to cloudwatch:<\/span><\/p>\n
          vim \/etc\/awslogs\/awslogs.conf<\/span>\r\n\r\n[\/mnt\/aem\/author\/crx-quickstart\/logs\/replication.log]<\/span>\r\n\r\ndatetime_format = %b %d %H:%M:%S<\/span>\r\n\r\nfile = \/mnt\/aem\/author\/crx-quickstart\/logs\/replication.log<\/span>\r\n\r\nbuffer_duration = 5000<\/span>\r\n\r\nlog_stream_name = {instance_id}<\/span>\r\n\r\ninitial_position = start_of_file<\/span>\r\n\r\nlog_group_name = Replication-log<\/span><\/pre>\n
          4. Start and enable <\/span>awslogsd <\/span><\/i>service by typing the command:<\/span><\/p>\n
          \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0sudo service awslogsd start<\/span>\r\n\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0sudo systemctl\u00a0 enable awslogsd<\/span>\r\n\r\n\r\n<\/pre>\n
          Step 3: Create an SNS Topic<\/b><\/p>\n
            \n
          1. Login to AWS Console<\/span><\/li>\n
          2. Search for SNS service<\/span><\/li>\n
          3. Navigate to SNS > Topic > Create Topic.<\/span><\/li>\n
          4. Select the Standard option and then Give your Topic name<\/span><\/li>\n<\/ol>\n
              \n
            • Now leave the rest of the options blank (Fill if required)<\/span><\/li>\n
            • Create the Topic<\/span><\/li>\n
            • Now we can add Subscriptions (Subjects whom we want to notify)<\/span><\/li>\n
            • Navigate to SNS > Subscriptions > Create Subscription<\/span><\/li>\n
            • Now Create Subscription\u00a0<\/span><\/li>\n
            • Select a Topic (Which we created earlier)<\/span><\/li>\n
            • Select Protocol (Email in our case)<\/span><\/li>\n
            • Select Endpoint (Email address in our case)<\/span><\/li>\n
            • Leave the rest of the options blank (fill in if necessary)<\/span><\/li>\n
            • Create a subscription.<\/span><\/li>\n
            • We can add multiple subscriptions to a single topic. <\/span><\/li>\n<\/ul>\n
              Step: 4: <\/b>Setup the Cloudwatch replication logger<\/b><\/p>\n
              Specify metric and conditions<\/span><\/p>\n
                \n
              • Navigate\u00a0 to Cloudwatch service -> log groups > log streams > metric filters<\/span><\/li>\n
              • Create metric filter<\/span><\/li>\n
              • Set the filter as \u201c<\/span>Failed<\/b>\u201d (if any Failed entry comes in the newly created replication log – SNS will trigger an alert)<\/span><\/li>\n
              • If we can keep the filter pattern as \u201c<\/span>401<\/b>\u201d – we will be notified if there is any unauthorized error in the replication log.<\/span><\/li>\n
              • Select your log stream.\u00a0<\/span><\/li>\n
              • Test the pattern<\/span><\/li>\n
              • Click on next<\/span><\/li>\n
              • Give the metric name<\/span><\/li>\n
              • Select Metric Namespace<\/span><\/li>\n
              • Give Metric Value (1 in our case)<\/span><\/li>\n<\/ul>\n
                Leave the rest and click on next.<\/span><\/p>\n
                  \n
                • Review and create and Metric<\/span><\/li>\n
                • Select the metric filter (checkbox in top-right corner) and click on \u201ccreate the alarm<\/span><\/li>\n
                • Select the Metric name<\/span><\/li>\n
                • Select the Statistics as \u201cSample Count\u201d<\/span><\/li>\n
                • Select Period accordingly (default : 5)<\/span><\/li>\n
                • Select Threshold type \u201cStatic\u201d\u2019<\/span><\/li>\n
                • Now select the condition Whenever <Metric Name> is \u201cGreater\/Equal\u201d\u00a0<\/span><\/li>\n
                • Than : <your value><\/span><\/li>\n<\/ul>\n
                  Select the additional configuration accordingly (Actions on Insufficient data)and the number of data points to alarm.<\/span><\/p>\n
                  Step 5: <\/b>Configure Notification details in the AWS SNS<\/b><\/p>\n
                    \n
                  1. Navigate to AWS SNS Service<\/span><\/li>\n
                  2. Define the alarm state trigger in the AWS SNS.<\/span><\/li>\n
                  3. IN ALARM > Select SNS Topic\u00a0<\/span><\/li>\n
                  4. Either select an existing topic Or create a topic<\/span><\/li>\n
                  5. Create another alarm for recovery alert when the replication queue is cleared.\u00a0<\/span><\/li>\n
                  6. Add name and description\u00a0<\/span><\/li>\n
                  7. Preview and create Alarm.<\/span><\/li>\n<\/ol>\n
                    Add the following commands to your \/.bashrc file to automatically reload the cloudwatch log; otherwise, on restarting the AEM instance, awslog will stop updating:<\/span><\/p>\n
                    sudo echo \"Starting awslogsd\"<\/span>\r\n\r\nsudo service awslogsd restart<\/span>\r\n\r\nsudo systemctl enable awslogsd<\/span>\r\n\r\nsudo systemctl status awslogsd<\/span><\/pre>\n
                    <\/div>","protected":false},"excerpt":{"rendered":"
                    This post will explain the approach to monitor the Replication Queues of Adobe Experience Manager (AEM) using AWS CloudWatch logs. Issue: The AEM content replication appears to be blocked. Editors can create content, but the activated pages on the CQ5 publish instance are not updated. Replication issues will occur with the following scenarios: The publisher […]<\/p>\n","protected":false},"author":1545,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":108},"categories":[5868,4682],"tags":[3573,5136,4847,5192],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/57141"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/1545"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=57141"}],"version-history":[{"count":2,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/57141\/revisions"}],"predecessor-version":[{"id":57286,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/57141\/revisions\/57286"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=57141"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=57141"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=57141"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}