|
@@ -36,7 +36,7 @@ logging driver options:
|
|
|
| Option | Required | Description |
|
|
|
|-----------------------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
|
| `splunk-token` | required | Splunk HTTP Event Collector token. |
|
|
|
-| `splunk-url` | required | Path to your Splunk Enterprise or Splunk Cloud instance (including port and schema used by HTTP Event Collector) `https://your_splunk_instance:8088`. |
|
|
|
+| `splunk-url` | required | Path to your Splunk Enterprise or Splunk Cloud instance (including port and scheme used by HTTP Event Collector) `https://your_splunk_instance:8088`. |
|
|
|
| `splunk-source` | optional | Event source. |
|
|
|
| `splunk-sourcetype` | optional | Event source type. |
|
|
|
| `splunk-index` | optional | Event index. |
|
|
@@ -53,7 +53,7 @@ Both options add additional fields to the attributes of a logging message.
|
|
|
Below is an example of the logging option specified for the Splunk Enterprise
|
|
|
instance. The instance is installed locally on the same machine on which the
|
|
|
Docker daemon is running. The path to the root certificate and Common Name is
|
|
|
-specified using an HTTPS schema. This is used for verification.
|
|
|
+specified using an HTTPS scheme. This is used for verification.
|
|
|
The `SplunkServerDefaultCert` is automatically generated by Splunk certificates.
|
|
|
|
|
|
docker run --log-driver=splunk \
|