Sentinel Destination Failing With 401 And 400 Errors Despite Working On Other Worker Groups This message originated from Cribl Community Slack.Click here to view the original link.Hey all, i'm troubleshooting a sentinel destination, trying to get SecurityEvent logs into the SecurityEvent table in sentinel, I have the same destination on 4 other worker groups, and they appear to be healthy. Allowed the traffic outbound to the Azure DCR url and login on my firewall so I don't believe there's a network error: Getting this error instead:
I have tried back pressure set to PQ, and it appeared to be writing into the disk and then set back to block to test around. I've already tried restarting the worker nodes and still getting the same error. I clone the destination on a different worker group again to test and it work. The volume isn't anything crazy, 20-30gb in total going through, or should be. I'm getting 401 and 400