-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update 3.7.0 -> 4.1.0 not working #207
Milestone
Comments
What version of SPLUNK are you using? |
Also, as a note this enhancement will probably be relevant. |
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[#207 (comment)], 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]
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.The text was updated successfully, but these errors were encountered: