Closed EEParker closed 6 months ago
@VictorioBerra If you have time I would like your opinion/review on these changes. Thank you
Looks like the link to the docs is dead: http://dev.splunk.com/view/SP-CAAAE6P
Is there a more up to date link describing the tiemstamp format and the precision?
https://docs.splunk.com/Documentation/Splunk/9.2.0/SearchReference/Commontimeformatvariables it looks like 3, 6 or 9 decimals are supported, so the PR probably needs to be updated to use an enum for millisecond, microseconds or nanoseconds.
That is very helpful! Thank you.
On Sat, Mar 16, 2024, 4:08 PM Jeff Parker, PE @.***> wrote:
https://docs.splunk.com/Documentation/Splunk/9.2.0/SearchReference/Commontimeformatvariables it looks like 3, 6 or 9 decimals are supported, so the PR probably needs to be updated to use an enum for millisecond, microseconds or nanoseconds.
— Reply to this email directly, view it on GitHub https://github.com/serilog-contrib/serilog-sinks-splunk/pull/172#issuecomment-2002133231, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAWMN27KKG6WPJCQJGRZHT3YYSYFPAVCNFSM6AAAAABEY7NQ7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBSGEZTGMRTGE . You are receiving this because you were mentioned.Message ID: @.***>
I've updated this PR with the enum, added unit tests and updated documentation links.
I've updated this PR with the enum, added unit tests and updated documentation links.
@VictorioBerra I added the test code and splunk props.conf to make this work in the sample project.
I've also verified that microseconds (6) work, but I couldn't get Splunk ingestion to work with nanoseconds (9). I believe this is on the Splunk side but I'm not sure what is needed.
Thanks for doing that, @EEParker can you share the changes you made to the props.conf? Maybe I could post on the Splunk forums about this?
Thanks for doing that, @EEParker can you share the changes you made to the props.conf? Maybe I could post on the Splunk forums about this?
props.conf
TIME_PREFIX = \"time\"\:\s*\"
TIME_FORMAT = %Y-%m-%dT%H:%M:%S.%9N%Z
Are you comfortable with merging this? I think a follow-up PR can be made to address any splunk samples that need to be changed. I would like to merge this in before #174.
@EEParker Yeah id say go ahead, I like the addition of the .editoconfig and the docker additions.
The first commit adds a sub-second decimal option to address #161.
The second commit adds a flag for disabling RenderedMessage per #167.
These both seem optional, but could be nice to have. I've included them here for review.