| 1 | 1 | The version of the syslog protocol specification. |
| 2 | 2019-08-01T17:21:59+00:00 | The date and time Cloud Platform forwarded this information to your external service. |
| 3 | web-00000 | The internal hostname of the infrastructure the log file originated from. For logs originating from Cloud Next, this field is |
| 4 | alphabeta.fpm-error | The internal Acquia site name this request is for, and type of log file, separated by a period. For production environments, each log entry contains: [sitename].[log-type]. For example, For non-production environments, each log entry contains: [sitename][env].[log-type]. For example,
|
| 5 | - | Process ID (pid). This field isn’t used. |
| 6 | - | Message ID (msg_id). This field isn’t used. |
If this content did not answer your questions, try searching or contacting our support team for further assistance.
| 1 | 1 | The version of the syslog protocol specification. |
| 2 | 2019-08-01T17:21:59+00:00 | The date and time Cloud Platform forwarded this information to your external service. |
| 3 | web-00000 | The internal hostname of the infrastructure the log file originated from. For logs originating from Cloud Next, this field is |
| 4 | alphabeta.fpm-error | The internal Acquia site name this request is for, and type of log file, separated by a period. For production environments, each log entry contains: [sitename].[log-type]. For example, For non-production environments, each log entry contains: [sitename][env].[log-type]. For example,
|
| 5 | - | Process ID (pid). This field isn’t used. |
| 6 | - | Message ID (msg_id). This field isn’t used. |
devdevIf this content did not answer your questions, try searching or contacting our support team for further assistance.