Log Forwarding - Limiting Scope of Logs being passed | Community
Skip to main content
P
Psythe
New Member
August 13, 2025
Solved

Log Forwarding - Limiting Scope of Logs being passed

  • August 13, 2025
  • 3 replies
  • 520 views

Hello there -

 

we setup the self service log forwarding (https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/log-forwarding#https) using https and so far its been working well but the logs are fairly large and sometimes causing issues with our API that receives them.

 

Is there a way, on the AEM config side, to select which logs are being passed? I know we can limit the aem and/or cdn logs only but we want to get more granular.

i.e.

 

  • aemaccess
  • aemerror
  • aemrequest
  • aemdispatcher
  • aemhttpdaccess
  • aemhttpderror

Can I set only the aemerror log from publisher or only the aemaccess log from author?

 

Thanks,

Best answer by VishalKa5

Hi @psythe ,

 

  • In AEM as a Cloud Service, self-service log forwarding lets you choose between AEM logs or CDN logs, but it does not support picking individual log files (like only aemerror or only aemaccess).

  • You cannot configure it to forward logs only from author or only from publishers either.

  • If you need that level of control, you must:

    • Filter on your side (after logs reach your API), or

    • Raise an Adobe feature request (RFE) to add finer log-level filtering.

Today, AEM config does not allow forwarding only specific logs (e.g., aemerror from publisher). Filtering must be handled outside AEM.

 

Thanks & Regards,

Vishal

3 replies

SantoshSai
Community Advisor
SantoshSaiCommunity Advisor
Community Advisor
August 13, 2025

Hi @psythe,

I think, you can use logForwarding.yaml for self-service configuration: AEM as a Cloud Service supports self-service log forwarding via a YAML configuration file (logForwarding.yaml) that you commit to your project's config directory and deploy via a Cloud Manager config pipeline.

You can specify which logs to forward using the data section. Supported log types include:

  • aemaccess

  • aemerror

  • aemrequest

  • aemdispatcher

  • aemhttpdaccess

  • aemhttpderror

  • aemcdn

Example configuration - only forward aemerror logs from publisher

kind: "LogForwarding"
version: "1"
metadata:
  envTypes: ["author","publish"]
data:
  splunk:  # or your target (e.g. Elasticsearch, Azure Blob, HTTPS, etc.)
    default:
      enabled: true
      host: "your-splunk-host"
      token: "${{SPLUNK_TOKEN}}"
      index: "aem_logs"
  forward:
    publish:
      - type: "aemerror"
    author:
      - type: "aemaccess"

  • envTypes sets which environment tiers (author, publish, stage, prod) the configuration applies to.

  • Under data, you define your logging destination.

  • The forward section lists exactly which log types to forward per tier.

This example forwards only aemerror logs from the publish environment and only aemaccess logs from author.

 

Reference: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/developing/log-forwarding

https://medium.com/tech-learnings/observability-in-aem-as-a-cloud-service-tools-techniques-and-best-practices-a78a3eef94da

Santosh Sai
    VishalKa5
    VishalKa5Accepted solution
    Level 5
    August 16, 2025

    Hi @psythe ,

     

    • In AEM as a Cloud Service, self-service log forwarding lets you choose between AEM logs or CDN logs, but it does not support picking individual log files (like only aemerror or only aemaccess).

    • You cannot configure it to forward logs only from author or only from publishers either.

    • If you need that level of control, you must:

      • Filter on your side (after logs reach your API), or

      • Raise an Adobe feature request (RFE) to add finer log-level filtering.

    Today, AEM config does not allow forwarding only specific logs (e.g., aemerror from publisher). Filtering must be handled outside AEM.

     

    Thanks & Regards,

    Vishal

      kautuk_sahni
      Community Manager
      kautuk_sahniCommunity Manager
      Community Manager
      August 21, 2025

      @psythe Just checking in. Were you able to resolve your issue? We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could benefit the community. Thanks again for being part of the conversation!

      Kautuk Sahni
      Terms & ConditionsAccessibility statement

      Loading footer...