Skip to main content
Solved

High Storage Usage On Hybrid Workers Despite Minimal Configuration

  • January 31, 2026
  • 1 reply
  • 0 views
J
This message originated from Cribl Community Slack.
Click here to view the original link.

Greetings all. How can I get a more detailed view into what is comprising the storage on my Hybrid workers? Although I recently started configuring the workergroup (handful of sources, destinations, and 4 routes), the wg storage is high with ~5 TB of 5.5 TB in use. I wouldn’t have expected it to be nearly maxed out. Additionally, some worker groups with no configurations and no data flowing through them are also nearing their storage limits. Persistent Queue isn’t enabled on any sources or destinations

Best answer by Yirmi

Hi Joe, I can't think of a place where we have that in the UI offhand, but here is how you can get that information from the Linux terminal. 1. Verify where your Cribl state directory resides (most likely /opt/cribl 2. from the Linux terminal of your worker's host, inspect the home directory size du -hs /opt/cribl 3. You can use du to drill down and inspect directories to find bloat 4. However, you should also check your state directory locations (if you, for example, map your S3 destination staging directory or PQ location to storage on a specific volume If you are using containers:
  • Inspect the location where your container's volumes map
  • Consider your deployment options to verify that your storage is properly handled when workers are replaced

1 reply

Y
  • Yirmi
  • New Participant
  • Answer
  • January 31, 2026
Hi Joe, I can't think of a place where we have that in the UI offhand, but here is how you can get that information from the Linux terminal. 1. Verify where your Cribl state directory resides (most likely /opt/cribl 2. from the Linux terminal of your worker's host, inspect the home directory size du -hs /opt/cribl 3. You can use du to drill down and inspect directories to find bloat 4. However, you should also check your state directory locations (if you, for example, map your S3 destination staging directory or PQ location to storage on a specific volume If you are using containers:
  • Inspect the location where your container's volumes map
  • Consider your deployment options to verify that your storage is properly handled when workers are replaced
Terms & ConditionsAccessibility statement