Splunk report some unpublished content still getting triggering | Community
Skip to main content
D
dh54220
Level 2
November 4, 2022
Solved

Splunk report some unpublished content still getting triggering

  • November 4, 2022
  • 1 reply
  • 845 views

Hi All,

 

We integrated AEM with Splunk to log monitoring In that report we found that some unpublished pages are still system is calling  unpublished content paths how we can debug Please give any suggestions.

 

Thankyou.

 

 

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Chandra_Hire

    Hi @dh54220 

    What I understood from your question is? - some page you have unpublished but still you can see paths for those pages in Splunk report. If my understanding is correct. then

     

    If the path is from access logs, then its okay as long as its redirecting to 404 page of the site. (It could be the case that these urls i.e. paths book marked by end users.

    1 reply

    Chandra_Hire
    Chandra_HireAccepted solution
    Level 4
    November 4, 2022

    Hi @dh54220 

    What I understood from your question is? - some page you have unpublished but still you can see paths for those pages in Splunk report. If my understanding is correct. then

     

    If the path is from access logs, then its okay as long as its redirecting to 404 page of the site. (It could be the case that these urls i.e. paths book marked by end users.

      D
      dh54220Author
      Level 2
      December 14, 2022

      Hi @chandra_hire 

      what you saying is the case is true for the content pages but in Splunk report we are getting some paths from OTB 

      like this /libs/cq/personalization

       

       

        Chandra_Hire
        Chandra_Hire
        Level 4
        December 14, 2022

        Hi @dh54220 

         

        If it is 404 for content pages it means no AEM resource being accessed and processed.  Please trace the referer path for /libs/cq/personalization (Not so sure but I believe, personalization being configured with AEM and there should be some other AEM resource (page/servlet/service) referring /libs/cq/personalization) and it could be from some component like header/footer (or any other component part of 404 page). 

         

        You can narrow down the Splunk logs by accessing path (which resolves to 404) to confirm whether /libs/cq/personalization is part of the 404 request.

         

          Terms & ConditionsAccessibility statement

          Loading footer...