fastly logging elasticsearch create

Create an Elasticsearch logging endpoint on a Fastly service version

Options

NameDescription
--name <name>The name of the Elasticsearch logging object. Used as a primary key for API access
--version <version>'latest', 'active', or the number of a specific version
--autocloneIf the selected service version is not editable, clone it and use the clone
--index <index>The name of the Elasticsearch index to send documents (logs) to. The index must follow the Elasticsearch index format rules (https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-create-index.html). We support strftime (http://man7.org/linux/man-pages/man3/strftime.3.html) interpolated variables inside braces prefixed with a pound symbol. For example, #{%F} will interpolate as YYYY-MM-DD with today's date
--url <url>The URL to stream logs to. Must use HTTPS
--service-id <service-id>Service ID (falls back to FASTLY_SERVICE_ID, then fastly.toml)
--service-name <service-name>The name of the service
--pipeline <pipeline>The ID of the Elasticsearch ingest pipeline to apply pre-process transformations to before indexing. For example my_pipeline_id. Learn more about creating a pipeline in the Elasticsearch docs (https://www.elastic.co/guide/en/elasticsearch/reference/current/ingest.html)
--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)
--format <format>Apache style log formatting. Your log must produce valid JSON that Elasticsearch 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