Multi-Experience Operations (MEO) runs on Cloud Platform infrastructure and supports log forwarding. Log forwarding enables you to send environment logs to an external logging or Security Information and Event Management (SIEM) service for centralized monitoring and analysis.
This page describes how log forwarding functions in MEO environments. For general information about log forwarding, including log file formats and troubleshooting, refer to Log forwarding in Cloud Platform.
Log Forwarding Eligibility
Log forwarding for MEO depends on contract terms and is not available by default. To confirm whether your subscription includes log forwarding, contact your Technical Account Manager (TAM) or Account Manager.
Prerequisites
Before configuring log forwarding, ensure that:
Log forwarding is enabled for your MEO subscription.
Your user role has one of the following permissions:
Administer log forwarding for non-production environments
Administer log forwarding for your production environment
You have the connection details for your logging service, such as the endpoint, port, token, and certificate, if required by your service.
Supported Destinations
MEO supports forwarding logs to the following services:
Splunk
Sumo Logic
Loggly
Syslog
Supported Log Types
Every log type supported by Cloud Platform is also supported in MEO. For additional information, refer to Using Logs with Codebases.
Drupal watchdog log forwarding is a core feature of Cloud Platform. You can forward Drupal watchdog logs to your own SIEM, such as Splunk.
Configure Log Forwarding for an Environment
You must set up log forwarding separately for each MEO environment, such as Production, UAT, Staging, and Development. Settings on one environment do not apply to other environments.
Select your codebase, and then select the environment to configure.
Select Logs and select Forward.
Select Add destination.
Select your log forwarding service.
Select the log types to forward.
Enter the connection details for your service.
Select Save.
Repeat these steps for each environment that requires log forwarding.
Logs typically begin forwarding within five minutes after you create a destination. You can check the status of each destination in the Status column on the Logs > Forward page. If logs do not arrive at your destination, refer to the troubleshooting information in Log forwarding in Cloud Platform.
Note
FedRAMP customers on MEO can configure Splunk log forwarding. Configure each environment separately in the Cloud Platform user interface. If the connection to your Splunk endpoint fails, create a Support ticket so Acquia can check the network routing configuration.
Limitations and Considerations
Per-environment setup: Log forwarding is not inherited across environments. Configure each environment separately.
Platform updates: Log streaming depends on the operating system version of the load balancers on the platform. Platform updates can occasionally disrupt log streaming. If logs stop arriving after a platform update, create a Support ticket.
If you have questions about log forwarding eligibility, contact your TAM or Account Manager. For configuration issues, create a Support ticket.
Log forwarding in Multi-Experience Operations
Multi-Experience Operations (MEO) runs on Cloud Platform infrastructure and supports log forwarding. Log forwarding enables you to send environment logs to an external logging or Security Information and Event Management (SIEM) service for centralized monitoring and analysis.
This page describes how log forwarding functions in MEO environments. For general information about log forwarding, including log file formats and troubleshooting, refer to Log forwarding in Cloud Platform.
Log Forwarding Eligibility
Log forwarding for MEO depends on contract terms and is not available by default. To confirm whether your subscription includes log forwarding, contact your Technical Account Manager (TAM) or Account Manager.
Prerequisites
Before configuring log forwarding, ensure that:
Log forwarding is enabled for your MEO subscription.
Your user role has one of the following permissions:
Administer log forwarding for non-production environments
Administer log forwarding for your production environment
You have the connection details for your logging service, such as the endpoint, port, token, and certificate, if required by your service.
Supported Destinations
MEO supports forwarding logs to the following services:
Splunk
Sumo Logic
Loggly
Syslog
Supported Log Types
Every log type supported by Cloud Platform is also supported in MEO. For additional information, refer to Using Logs with Codebases.
Drupal watchdog log forwarding is a core feature of Cloud Platform. You can forward Drupal watchdog logs to your own SIEM, such as Splunk.
Configure Log Forwarding for an Environment
You must set up log forwarding separately for each MEO environment, such as Production, UAT, Staging, and Development. Settings on one environment do not apply to other environments.
Select your codebase, and then select the environment to configure.
Select Logs and select Forward.
Select Add destination.
Select your log forwarding service.
Select the log types to forward.
Enter the connection details for your service.
Select Save.
Repeat these steps for each environment that requires log forwarding.
Logs typically begin forwarding within five minutes after you create a destination. You can check the status of each destination in the Status column on the Logs > Forward page. If logs do not arrive at your destination, refer to the troubleshooting information in Log forwarding in Cloud Platform.
Note
FedRAMP customers on MEO can configure Splunk log forwarding. Configure each environment separately in the Cloud Platform user interface. If the connection to your Splunk endpoint fails, create a Support ticket so Acquia can check the network routing configuration.
Limitations and Considerations
Per-environment setup: Log forwarding is not inherited across environments. Configure each environment separately.
Platform updates: Log streaming depends on the operating system version of the load balancers on the platform. Platform updates can occasionally disrupt log streaming. If logs stop arriving after a platform update, create a Support ticket.
If you have questions about log forwarding eligibility, contact your TAM or Account Manager. For configuration issues, create a Support ticket.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Multi-Experience Operations