Configure gRCP 🔗

gRPC exposes a variety of settings you can adjust within individual receivers or exporters of the Collector.

Note

To configure transport, see Configure network settings.

Configure gRCP clients 🔗

To configure gRCP clients in exporters use these settings:

auth. See Configure authentication
balancer_name
- Defaults: pick_first before version 0.103.0, round_robin for v0.103.0 or higher
- Learn more at gRCP’s Load Balancing README .
compression
- Compression type valid values are gzip, snappy, zstd, and none
endpoint
- For valid syntax see gRPC Name Resolution .
headers
keepalive
read_buffer_size
tls. See Configure TLS.
write_buffer_size

For example:

exporters:
   otlp:
      endpoint: otelcol2:55690
      auth:
         authenticator: some-authenticator-extension
      tls:
         ca_file: ca.pem
         cert_file: cert.pem
         key_file: key.pem
      headers:
         test1: "value1"
         "test 2": "value 2"

Configure gRCP servers 🔗

To configure gRCP servers in collector receivers use these settings:

auth. See Configure authentication
keepalive
max_concurrent_streams
max_recv_msg_size_mib
read_buffer_size
tls. See Configure TLS
write_buffer_size

Learn more 🔗

For more details on the available settings refer to:

gRPC Configuration Settings in OTel’s GitHub repo
Golang’s gRCP documentation

This page was last updated on Oct 08, 2024.

Was this topic useful?

Did you know that you can edit this page? Learn how!

Was this documentation topic helpful?

Enter your email address if you would like someone from the documentation team to reply to your question or suggestion.

Please provide your comments here. Ask a question or make a suggestion.

Comment should have a minimum of 5 characters and a maximum of 1,000 characters.

Feedback submitted, thank you! We resolve documentation feedback based on the severity of the issue reported, as well as an assessment of the potential number of customers who might be affected.

If you have a question about using Splunk software, we encourage you to check Splunk Answers or Splunk community Slack to see if similar questions have been answered, or to post your question for others to answer. If you have an active support entitlement and believe that your situation is caused by a product defect, file a support case in the Support portal https://login.splunk.com/page/sso_redirect?type=portal.

We are currently moving to a new documentation site. Expect a delay in responding to your feedback and applying any updates based on your feedback. Thank you for your patience and understanding while we work to bring you an improved documentation experience!