fastly logging https create
Create an HTTPS logging endpoint on a Fastly service version
Options
| Name | Description |
|---|---|
--name <name> | The name of the HTTPS logging object. Used as a primary key for API access |
--version <version> | 'latest', 'active', or the number of a specific version |
--autoclone | If the selected service version is not editable, clone it and use the clone |
--url <url> | URL that log data will be sent to. Must use the https protocol |
--service-id <service-id> | Service ID (falls back to FASTLY_SERVICE_ID, then fastly.toml) |
--service-name <service-name> | The name of the service |
--content-type <content-type> | Content type of the header sent with the request |
--header-name <header-name> | Name of the custom header sent with the request |
--header-value <header-value> | Value of the custom header sent with the request |
--method <method> | HTTP method used for request. Can be POST or PUT. Defaults to POST if not specified |
--json-format <json-format> | Enforces valid JSON formatting for log entries. Can be disabled 0, array of json (wraps JSON log batches in an array) 1, or newline delimited json (places each JSON log entry onto a new line in a batch) 2 |
--tls-ca-cert <tls-ca-cert> | A secure certificate to authenticate the server with. Must be in PEM format |
--tls-client-cert <tls-client-cert> | The client certificate used to make authenticated requests. Must be in PEM format |
--tls-client-key <tls-client-key> | The client private key used to make authenticated requests. Must be in PEM format |
--tls-hostname <tls-hostname> | The hostname used to verify the server's certificate. It can either be the Common Name or a Subject Alternative Name (SAN) |
--message-type <message-type> | How the message should be formatted. One of: classic (default), loggly, logplex or blank |
--format <format> | Apache style log formatting. Your log must produce valid JSON that HTTPS can ingest |
--format-version <format-version> | The version of the custom logging format used for the configured endpoint. Can be either 2 (default) or 1 |
--placement <placement> | Where in the generated VCL the logging call should be placed, overriding any format_version default. Can be none or waf_debug |
--response-condition <response-condition> | The name of an existing condition in the configured endpoint, or leave blank to always execute |
--request-max-entries <request-max-entries> | Maximum number of logs to append to a batch, if non-zero. Defaults to 10k |
--request-max-bytes <request-max-bytes> | Maximum size of log batch, if non-zero. Defaults to 100MB |