Cribl LogStream can send log and metric events to Sumo Logic over HTTP.
Configuring Cribl LogStream to Output to Sumo Logic
In the QuickConnect UI: Click + Add beside Destinations. From the resulting drawer's tiles, select Sumo Logic. Next, click either + Add New or (if displayed) Select Existing. The resulting drawer will provide the following options and fields.
Or, in the Data Routes UI: From the top nav of a LogStream instance or Group, select Data > Destinations. From the resulting page's tiles or the Destinations left nav, select Sumo Logic. Next, click + Add New to open a New Destination modal that provides the following options and fields.
Output ID: Enter a unique name to identify this Sumo Logic Destination definition.
API URL: Enter the URL of the Sumo Logic HTTP collector to which events should be sent. (E.g.,
Custom source name: Optionally, override the source
name configured on the Sumo Logic HTTP collector. This value will be sent with events via the
X‑Sumo‑Name HTTP header.
Custom source category: Optionally, override the source
category configured on the Sumo Logic HTTP collector. This value will be sent with events via the
X‑Sumo‑Category HTTP header.
Backpressure behavior: Whether to block, drop, or queue events when all receivers are exerting backpressure.
Persistent Queue Settings
This section is displayed when the Backpressure behavior is set to Persistent Queue.
Max file size: The maximum size to store in each queue file before closing it. Enter a numeral with units of KB, MB, etc. Defaults to
Max queue size: The maximum amount of disk space the queue is allowed to consume. Once this limit is reached, queueing is stopped, and data blocking is applied. Enter a numeral with units of KB, MB, etc.
Queue file path: The location for the persistent queue files. This will be of the form:
your/path/here/<worker-id>/<output-id>. Defaults to
Compression: Codec to use to compress the persisted data, once a file is closed. Defaults to
Gzip is also available.
Queue-full behavior: Whether to block or drop events when the queue is exerting backpressure (because disk is low or at full capacity). Block is the same behavior as non-PQ blocking, corresponding to the Block option on the Backpressure behavior drop-down. Drop new data throws away incoming data, while leaving the contents of the PQ unchanged.
Pipeline: Pipeline to process data before sending the data out using this output.
System fields: A list of fields to automatically add to events that use this output. By default, includes
cribl_pipe (identifying the LogStream Pipeline that processed the event). Supports wildcards. Other options include:
cribl_host– LogStream Node that processed the event.
cribl_wp– LogStream Worker Process that processed the event.
cribl_input– LogStream Source that processed the event.
cribl_output– LogStream Destination that processed the event.
Validate server certs: Toggle to
Yes to reject certificates that are not authorized by a CA in the CA certificate path, nor by another trusted CA (e.g., the system's CA).
Round-robin DNS: Toggle to
Yes to use round-robin DNS lookup. When a DNS server returns multiple addresses, this will cause LogStream to cycle through them in the order returned.
Compress: Toggle this slider to
Yes to compress the payload body before sending.
Request timeout: Amount of time (in seconds) to wait for a request to complete before aborting it. Defaults to
Request concurrency: Maximum number of concurrent requests before blocking. This is set per Worker Process. Defaults to
Max body size (KB): Maximum size of the request body. Defaults to
Flush period (sec): Maximum time between requests. Low values could cause the payload size to be smaller than its configured maximum. Defaults to
Extra HTTP headers: Name/Value pairs to pass as additional HTTP headers.
Environment: If you're using GitOps, optionally use this field to specify a single Git branch on which to enable this configuration. If empty, the config will be enabled everywhere.
Cribl LogStream uses a set of internal fields to assist in forwarding data to a Destination.
If an event contains the internal field
__criblMetrics, LogStream will send it to Sumo Logic as a metric event. Otherwise, LogStream will send it as a log event.
Notes on HTTP-based Outputs
Cribl LogStream will attempt to use keepalives to reuse a connection for multiple requests. After 2 minutes of the first use, the connection will be thrown away, and a new one will be reattempted. This is to prevent sticking to a particular destination when there is a constant flow of events.
If the server does not support keepalives (or if the server closes a pooled connection while idle), a new connection will be established for the next request.
When resolving the Destination's hostname, LogStream will pick the first IP in the list for use in the next connection. Enable Round-robin DNS to better balance distribution of events between destination cluster nodes.