fastly logging syslog create

Create a Syslog logging endpoint on a Fastly service version


--name <name>The name of the Syslog 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
--address <address>A hostname or IPv4 address
--service-id <service-id>Service ID (falls back to FASTLY_SERVICE_ID, then fastly.toml)
--service-name <service-name>The name of the service
--port <port>The port number
--use-tlsWhether to use TLS for secure logging. Can be either true or false
--tls-ca-cert <tls-ca-cert>A secure certificate to authenticate the server with. Must be in PEM format
--tls-hostname <tls-hostname>Used during the TLS handshake to validate the certificate
--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
--auth-token <auth-token>Whether to prepend each message with a specific token
--format <format>Apache style log formatting
--format-version <format-version>The version of the custom logging format used for the configured endpoint. Can be either 2 (default) or 1
--message-type <message-type>How the message should be formatted. One of: classic (default), loggly, logplex or blank
--response-condition <response-condition>The name of an existing condition in the configured endpoint, or leave blank to always execute
--placement <placement>Where in the generated VCL the logging call should be placed, overriding any format_version default. Can be none or waf_debug