Sumologic
Fastly will POST messages to the Sumo Logic account in the format specified in the Sumologic object.
Data model
message_type | string | How the message should be formatted. [Default classic] | |
url | string | The URL to post logs to. | |
format | string | A Fastly log format string. [Default %h %l %u %t "%r" %>s %b] | |
format_version | integer | The version of the custom logging format used for the configured endpoint. The logging call gets placed by default in vcl_log if format_version is set to 2 and in vcl_deliver if format_version is set to 1. [Default 2] | |
name | string | The name for the real-time logging configuration. | |
placement | string | Where in the generated VCL the logging call should be placed. If not set, endpoints with format_version of 2 are placed in vcl_log and those with format_version of 1 are placed in vcl_deliver. | |
response_condition | string | The name of an existing condition in the configured endpoint, or leave blank to always execute. | |
created_at | string | Date and time in ISO 8601 format. Read-only. | |
deleted_at | string | Date and time in ISO 8601 format. Read-only. | |
service_id | string | Alphanumeric string identifying the service. Read-only. | |
updated_at | string | Date and time in ISO 8601 format. Read-only. | |
version | string | String identifying a service version. Read-only. |
Endpoints
GET/service/service_id/version/version_id/logging/sumologic/logging_sumologic_name
PUT/service/service_id/version/version_id/logging/sumologic/logging_sumologic_name
User contributed notes
BETADo you see an error in this page? Do have an interesting use case, example or edge case people should know about? Share your knowledge and help people who are reading this page! (Comments are moderated; for support, please contact support@fastly.com)