/
config.yaml
95 lines (93 loc) · 3.37 KB
/
config.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
receivers:
# The following entry initializes the default OTLP receiver.
# The full name of this receiver is `otlp` and can be referenced in pipelines by 'otlp'.
otlp:
protocols:
grpc:
http:
# The following entry initializes the default OTLP receiver with only gRPC support.
otlp/only_grpc:
protocols:
grpc:
# The following entry initializes the default OTLP receiver with only http support.
otlp/only_http:
protocols:
http:
# The following entry demonstrates configuring the common receiver settings:
# - endpoint
# This configuration is of type 'otlp' and has the name 'customname' with a full name of 'otlp/customname'
# ('<type>/<name>'. To reference this configuration in a pipeline, use the full name `otlp/customname`.
otlp/customname:
protocols:
grpc:
# The receiver will listen on endpoint: "localhost:9090".
endpoint: localhost:9090
# The following entry configures all of the keep alive settings. These settings are used to configure the receiver.
otlp/keepalive:
protocols:
grpc:
keepalive:
server_parameters:
max_connection_idle: 11s
max_connection_age: 12s
max_connection_age_grace: 13s
time: 30s
timeout: 5s
enforcement_policy:
min_time: 10s
permit_without_stream: true
# The following demonstrates how to set maximum limits on stream, message size and connection idle time.
# Note: The test yaml has demonstrated configuration on a grouped by their structure; however, all of the settings can
# be mix and matched like adding the maximum connection idle setting in this example.
otlp/msg-size-conc-connect-max-idle:
protocols:
grpc:
max_recv_msg_size_mib: 32
max_concurrent_streams: 16
read_buffer_size: 1024
write_buffer_size: 1024
keepalive:
server_parameters:
max_connection_idle: 10s
# The following entry demonstrates how to specify TLS credentials for the server.
# Note: These files do not exist. If the receiver is started with this configuration, it will fail.
otlp/tlscredentials:
protocols:
grpc:
tls_settings:
cert_file: test.crt
key_file: test.key
http:
tls_settings:
cert_file: test.crt
key_file: test.key
# The following entry demonstrates how to specify a Unix Domain Socket for the server.
otlp/uds:
protocols:
grpc:
transport: unix
endpoint: /tmp/grpc_otlp.sock
http:
# transport: unix
endpoint: /tmp/http_otlp.sock
# The following entry demonstrates how to configure the OTLP receiver to allow Cross-Origin Resource Sharing (CORS).
# Both fully qualified domain names and the use of wildcards are supported.
otlp/cors:
protocols:
http:
cors_allowed_origins:
- https://*.test.com # Wildcard subdomain. Allows domains like https://www.test.com and https://foo.test.com but not https://wwwtest.com.
- https://test.com # Fully qualified domain name. Allows https://test.com only.
processors:
exampleprocessor:
exporters:
exampleexporter:
service:
pipelines:
traces:
receivers: [otlp/customname]
processors: [exampleprocessor]
exporters: [exampleexporter]
metrics:
receivers: [otlp]
exporters: [exampleexporter]