The log forwarding certificates for Splunk, Sumologic, and other syslog destinations must have an expiry greater than 30 days.
Log forwarding is a paid service. To enable log forwarding for your subscription, contact your account manager.
Many websites must forward their log files to a central location (such as Sumologic, Splunk, or Loggly) for processing and alerting. Acquia uses TLS over TCP to forward the log files you select to a remote destination.
All Cloud Platform subscribers can access Acquia-provided log files in the Cloud Platform interface. For more information, see Streaming log entries in real time.
Configuring log forwarding
After log forwarding is enabled for you, assign the Administer log forwarding for non-production environments and Administer log forwarding for your production environmentpermissions to roles in your organization. By default, the Team Lead and Senior Developer roles can manage log forwarding on all environments, while the Developer role can manage log forwarding on non-production environments only.
To configure log forwarding for Cloud Platform, a user with one of the log forwarding permissions must complete the following steps depending on the log forwarding service you have selected:
All logs forwarded to your remote destination have additional fields added to the beginning of each line. For more information about this data and its format, see File formats in forwarded log files.
Determining the log forwarding status
The Cloud Platform user interface allows you to determine the status of the log forwarding process for each of your logs. A log forwarding destination may have one of the following statuses:
Active: Cloud Platform is actively forwarding your logs to the log forwarding destination. The Cloud Platform user interface will display the active text along with an Active icon in the Status column of the Logs > Forward page.
Inactive: Cloud Platform is not actively forwarding your logs to the log forwarding destination. The Cloud Platform user interface will display the inactive text along with an Inactive icon in the Status column of the Logs > Forward page.
Pending: The Cloud Platform log forwarding process is in the pending state during the time it takes a user to complete the following actions:
Create a log forwarding destination
Edit a log forwarding destination
Enable a log forwarding destination
Disable a log forwarding destination
The Cloud Platform user interface will display the pending text along with the Pending icon in the Status column of the Logs > Forward page.
Legacy log forwarding service
If your application is currently using Acquia’s legacy log forwarding service, contact your Technical Account Manager (TAM) or Acquia Support to learn more about upgrading to the current version of the service.
Note
Acquia Support can only assist with troubleshooting issues related to the new log forwarding infrastructure or customer interface, and cannot assist with troubleshooting issues related to third-party services.
Cloud Platform API endpoints for log forwarding
The Cloud Platform API provides endpoints for log forwarding, including:
The log forwarding certificates for Splunk, Sumologic, and other syslog destinations must have an expiry greater than 30 days.
Log forwarding is a paid service. To enable log forwarding for your subscription, contact your account manager.
Many websites must forward their log files to a central location (such as Sumologic, Splunk, or Loggly) for processing and alerting. Acquia uses TLS over TCP to forward the log files you select to a remote destination.
All Cloud Platform subscribers can access Acquia-provided log files in the Cloud Platform interface. For more information, see Streaming log entries in real time.
Configuring log forwarding
After log forwarding is enabled for you, assign the Administer log forwarding for non-production environments and Administer log forwarding for your production environmentpermissions to roles in your organization. By default, the Team Lead and Senior Developer roles can manage log forwarding on all environments, while the Developer role can manage log forwarding on non-production environments only.
To configure log forwarding for Cloud Platform, a user with one of the log forwarding permissions must complete the following steps depending on the log forwarding service you have selected:
All logs forwarded to your remote destination have additional fields added to the beginning of each line. For more information about this data and its format, see File formats in forwarded log files.
Determining the log forwarding status
The Cloud Platform user interface allows you to determine the status of the log forwarding process for each of your logs. A log forwarding destination may have one of the following statuses:
Active: Cloud Platform is actively forwarding your logs to the log forwarding destination. The Cloud Platform user interface will display the active text along with an Active icon in the Status column of the Logs > Forward page.
Inactive: Cloud Platform is not actively forwarding your logs to the log forwarding destination. The Cloud Platform user interface will display the inactive text along with an Inactive icon in the Status column of the Logs > Forward page.
Pending: The Cloud Platform log forwarding process is in the pending state during the time it takes a user to complete the following actions:
Create a log forwarding destination
Edit a log forwarding destination
Enable a log forwarding destination
Disable a log forwarding destination
The Cloud Platform user interface will display the pending text along with the Pending icon in the Status column of the Logs > Forward page.
Legacy log forwarding service
If your application is currently using Acquia’s legacy log forwarding service, contact your Technical Account Manager (TAM) or Acquia Support to learn more about upgrading to the current version of the service.
Note
Acquia Support can only assist with troubleshooting issues related to the new log forwarding infrastructure or customer interface, and cannot assist with troubleshooting issues related to third-party services.
Cloud Platform API endpoints for log forwarding
The Cloud Platform API provides endpoints for log forwarding, including:
(Optional) In the Copy existing destination section, click Select Destination to copy and use the values from an existing log forwarding configuration of another environment.
In the Name of destination field, enter a human-readable name for the destination of the forwarded logs.
In the Token field, enter a token for securely sending your logs to the consuming service. For more information about customer tokens, see Loggly’s documentation..
Select one or more checkboxes for the log files you want to forward to this destination:
Click Submit. Cloud Platform will display the list of log forwarding destinations for this subscription.
After you create a log forwarding destination, Cloud Platform-created logs should begin forwarding to your remote destination within five minutes. If logs do not appear at your remote destination based on this expectation, review Common issues with log forwarding. If issues persist, 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.
To configure log forwarding for Loggly, complete the following steps:
(Optional) In the Copy existing destination section, click Select Destination to copy and use the values from an existing log forwarding configuration of another environment.
In the Name of destination field, enter a human-readable name for the destination of the forwarded logs.
In the Token field, enter a token for securely sending your logs to the consuming service. For more information about customer tokens, see Loggly’s documentation..
Select one or more checkboxes for the log files you want to forward to this destination:
Click Submit. Cloud Platform will display the list of log forwarding destinations for this subscription.
After you create a log forwarding destination, Cloud Platform-created logs should begin forwarding to your remote destination within five minutes. If logs do not appear at your remote destination based on this expectation, review Common issues with log forwarding. If issues persist, 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.
Cloud Platform