go-syslog
go-syslog copied to clipboard
influxdata
Allow skipping Pri header.
following this issue.
in the new standard (RFC 5424) it stated that 'Facility and Severity values are not normative but often used.' meaning that the pri header is not mandatory. as a result, multiple products are sending Syslog messages without the pri header. Also, RFC3164 in the pri header section talks about relay messages and implies that it might not be mandatory in other non-relaying options.
so I added a new option to allow skipping the pri header. this is highly important for our use case.
@leodido @powersj @jdstrand I saw that you were the last to comment/confirm something on this repository. I would greatly appreciate it if one of you could spare a few minutes for this
it doesn't seem related to my changes, as I didn't change the parser code. but I'll try to run it locally
@powersj thank you very much for taking a look. the issue was that the parser test was using the machine test cases. it seems to be OK now.
BTW, how do you build the project? running 'make build' doesn't seem to work for me. it's not running the ' ragel -I common -Z -G2 -e -o rfc3164/machine.go rfc3164/machine.go.rl' command and as a result, I don't see my changes reflecting in the machine.go file. only after running the command manually it seems to work.
the issue was that the parser test was using the machine test cases. it seems to be OK now.
Thanks for looking into it!
BTW, how do you build the project? running 'make build' doesn't seem to work for me. it's not running...
heh, I basically ran make build and make tests when I took my first look at this.
I don't have anymore write/maintain access here. So, I can't help/maintain it. It's unfortunate but it is what it is... Feel free to redirect this PR to https://github.com/leodido/go-syslog. I plan to keep evolving this project there, on my GitHub. Thank you
I don't have anymore write/maintain access here. So, I can't help/maintain it. It's unfortunate but it is what it is...
Your last commit was from 3 years ago :) If this is something you are interested in picking back up again, then we can revisit that. However, happy to see you pick up your own fork as well.