Integrating Cribl Lake with Cribl Edge
Archive your Cribl Edge data to Cribl Lake, via Cribl Stream.
To send data from Cribl Edge to Cribl Lake, you need to route it through Cribl Stream, using the Cribl HTTP or Cribl TCP Destination/Source pair. Either option prevents double billing when you ingest the data from Edge to Stream.
The main steps are:
- Send data from Cribl Edge to a Stream Worker Group.
- Receive data in Cribl Stream.
- Send data from Cribl Stream to Cribl Lake.
To learn more about communicating between Cribl Edge and Cribl Stream, see the Cribl Edge to Cribl Stream guide.
The Edge Getting Started tutorial presents a similar use case with detailed steps for configuring the Cribl HTTP Sources and Destination to seamlessly send data between Edge and Stream.
Send Data from Cribl Edge
- In Cribl Edge, create a new Cribl HTTP Destination. (You could also use Cribl TCP, but this example will use the former.)
- Next, use QuickConnect to pass your Edge data to this Destination.
Receive Data in Cribl Stream
- In Cribl Stream, create a new Cribl HTTP Source.
- Make sure that the Address and Port fields in the Source’s configuration correspond to what you configured in Cribl Edge.
Send Data to Cribl Lake
- Once data is flowing from Cribl Edge to Cribl Stream, create a Cribl Lake Destination in the same Worker Group.
- Select the Lake Dataset you want to use as the target for the Destination.
- Finally, connect the Cribl HTTP Source with the new Cribl Lake Destination via QuickConnect.
Verify Data Flow
To make sure that data is flowing correctly into Cribl Lake, you can run a test search over the selected Lake Dataset.