@@ -18,30 +18,41 @@ This distribution comes with a [default
18
18
configuration] ( https://github.com/signalfx/splunk-otel-collector/blob/main/cmd/otelcol/config/collector/splunk_config.yaml )
19
19
which requires the following environment variables:
20
20
21
- - ` ${SPLUNK_REALM} ` : Which realm to send the data to (for example: ` us0 ` )
22
- - ` ${SPLUNK_ACCESS_TOKEN} ` : Access token to authenticate requests
23
- - ` ${SPLUNK_BALLAST_SIZE_MIB} ` : How much memory to allocate to the ballast. This should be set to 1/3 to 1/2 of configured memory.
21
+ - ` SPLUNK_REALM ` (no default): Which realm to send the data to (for example: ` us0 ` )
22
+ - ` SPLUNK_ACCESS_TOKEN ` (no default): Access token to authenticate requests
23
+ - ` SPLUNK_BALLAST_SIZE_MIB ` (no default): How much memory to allocate to the ballast. This should be set to 1/3 to 1/2 of configured memory.
24
+
25
+ In addition, the following environment variables are optional:
26
+
27
+ - ` SPLUNK_CONFIG ` (default = ` /etc/otel/collector/splunk-config_linux.yaml ` ): Which configuration to load.
28
+ - ` SPLUNK_MEMORY_LIMIT_PERCENTAGE ` (default = ` 90 ` ): Maximum amount of total memory targeted to be allocated by the process heap.
29
+ - ` SPLUNK_MEMORY_SPIKE_PERCENTAGE ` (default = ` 20 ` ): Maximum spike expected between the measurements of memory usage.
30
+
31
+ When running on a non-linux system, the following environment variables are required:
32
+
33
+ - ` SPLUNK_CONFIG ` (default = ` /etc/otel/collector/splunk-config_non_linux.yaml ` ): Which configuration to load.
34
+ - ` SPLUNK_MEMORY_LIMIT_MIB ` (no default): Maximum amount of total memory targeted to be allocated by the process heap.
35
+ - ` SPLUNK_MEMORY_SPIKE_MIB ` (no default): Maximum spike expected between the measurements of memory usage.
24
36
25
37
Deploy the collector as outlined in the below. More information
26
38
about deploying and configuring the collector can be found
27
39
[ here] ( https://docs.signalfx.com/en/latest/apm/apm-getting-started/apm-opentelemetry-collector.html )
28
40
29
41
### Docker
30
42
31
- Deploy from a Docker container (replace ` 0.1.0-otel-0.11.0 ` with the latest
32
- stable version number if necessary):
43
+ Deploy from a Docker container (replace ` 0.1.0 ` with the latest stable version number if necessary):
33
44
34
45
``` bash
35
46
$ SPLUNK_REALM=us0 SPLUNK_ACCESS_TOKEN=12345 SPLUNK_BALLAST_SIZE_MIB=683 \
36
- docker run -p 7276:7276 -p 8888:8888 -p 9943:9943 -p 55679:55679 -p 55680:55680 -p 9411:9411 \
37
- --name otelcol signalfx/splunk-otel-collector:0.1.0-otel-0.11.0
47
+ docker run -p 13133 -p 14250 -p 14268 -p 55678-55680 -p 6060 -p 7276 -p 8888 -p 9411 -p 9943 \
48
+ --name otelcol signalfx/splunk-otel-collector:0.1.0
38
49
```
39
50
40
51
### Kubernetes
41
52
42
- To deploy the OpenTelemetry Collector in Kubernetes, create a configuration
43
- file that defines a ConfigMap, Service, and Deployment for the cluster. For
44
- more information about creating a configuration file, see the example
53
+ To deploy in Kubernetes, create a configuration file that defines a ConfigMap,
54
+ Service, and Deployment for the cluster. For more information about creating a
55
+ configuration file, see the example
45
56
[ signalfx-k8s.yaml] ( https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/master/exporter/sapmexporter/examples/signalfx-k8s.yaml )
46
57
file on GitHub.
47
58
@@ -53,19 +64,35 @@ $ SPLUNK_REALM=us0 SPLUNK_ACCESS_TOKEN=12345 SPLUNK_BALLAST_SIZE_MIB=683 \
53
64
./bin/otelcol
54
65
```
55
66
56
- ## Custom Configuration
67
+ ## Advanced Configuration
68
+
69
+ ### Command Line Arguments
70
+
71
+ Following the binary command or Docker container command line arguments can be
72
+ specified. Command line arguments take priority over environment variables.
73
+
74
+ For example in Docker:
75
+
76
+ ``` bash
77
+ $ SPLUNK_REALM=us0 SPLUNK_ACCESS_TOKEN=12345 SPLUNK_BALLAST_SIZE_MIB=683 \
78
+ docker run -p 13133 -p 14250 -p 14268 -p 55678-55680 -p 6060 -p 7276 -p 8888 -p 9411 -p 9943 \
79
+ -v collector.yaml:/etc/collector.yaml:ro \
80
+ --name otelcol signalfx/splunk-otel-collector:0.1.0 \
81
+ --log-level=DEBUG
82
+ ```
83
+
84
+ ### Custom Configuration
57
85
58
86
In addition to using the default configuration, a custom configuration can also
59
87
be provided.
60
88
61
89
For example in Docker:
62
90
63
91
``` bash
64
- $ SPLUNK_REALM=us0 SPLUNK_ACCESS_TOKEN=12345 SPLUNK_BALLAST_SIZE_MIB=683 \
65
- docker run -p 7276:7276 -p 8888:8888 -p 9943:9943 -p 55679:55679 -p 55680:55680 -p 9411:9411 \
92
+ $ SPLUNK_REALM=us0 SPLUNK_ACCESS_TOKEN=12345 SPLUNK_BALLAST_SIZE_MIB=683 SPLUNK_CONFIG=/etc/collector.yaml \
93
+ docker run -p 13133 -p 14250 -p 14268 -p 55678-55680 -p 6060 -p 7276 -p 8888 -p 9411 -p 9943 \
66
94
-v collector.yaml:/etc/collector.yaml:ro \
67
- --name otelcol signalfx/splunk-otel-collector:0.1.0-otel-0.11.0 \
68
- --config /etc/collector.yaml
95
+ --name otelcol signalfx/splunk-otel-collector:0.1.0
69
96
```
70
97
71
98
Note that if the configuration includes a memorylimiter processor then it must set the
0 commit comments