Closed HalHaynes closed 5 months ago
What version of SPLUNK are you using?
Also, as a note this enhancement will probably be relevant. https://github.com/serilog-contrib/serilog-sinks-splunk/issues/205#issuecomment-2130025620
Had the same issue, I've manually set the uriPath to "services/collector" and worked. Splunk version 9.1.2308.203
I'm going to close this issue and use 205 for tracking the work.
Splunk Enterprise 9.1.4
May 28, 2024 11:12:40 Jeff Parker, PE @.***>:
What version of SPLUNK are you using?
— Reply to this email directly, view it on GitHub[https://github.com/serilog-contrib/serilog-sinks-splunk/issues/207#issuecomment-2135480408], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ALOC6ZJB6FJ3NSBHOXUZN2TZESNGPAVCNFSM6AAAAABIIELUGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZVGQ4DANBQHA]. You are receiving this because you authored the thread. [Tracking image][https://github.com/notifications/beacon/ALOC6ZLQ6OU4AH2YQHKDUC3ZESNGPA5CNFSM6AAAAABIIELUGKWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTT7JDMFQ.gif]
While updating a variety of packages in my application, I updated Serilog.Sinks.Splunk from 3.7.0 to 4.1.0 and discovered that nothing was getting written to Splunk after that. I found the breaking change at https://github.com/serilog-contrib/serilog-sinks-splunk/wiki that says to change
services/collector
toservices/collector/event
, so I did that. But it didn't work. I reverted to my previous commit and the Splunk logging started to happen again.