@wrcombs said in What Are You Doing Right Now:
@momurda said in What Are You Doing Right Now:
@wrcombs said in What Are You Doing Right Now:
Not a single call has came in since 8:00 this morning. . .
Im watching F1 practice session from the Putin Federation, then ill watch fp2, then I will try to go home by noon.
wish i could go home early.
Just got out of a three hour meeting. I can relate to this feeling.
@DustinB3403 said in Why IT Builds a House of Cards:
Just to necro this thread, how would someone in IT actually get the business to see and understand these risks? I've tried this, explained in full detail the chances taken and I get a "thank you for telling us, but let's stay the course" sorts of responses.
Thanks for the necro. Get greeted with a comment I didn't recall making, just to look at the date 2 1/2 years ago. lol.
Then, on a second note, this article legitimately applies to me today.
I think my approach to this would be this: Keep your endpoints simple.
Take a look at what the system comes with. From a quick check, I'm almost certain both CentOS and Fedora ship with rsyslog, which would lead me to believe that the Pi would have that or something very similar. If not, rsyslog does at least have an ARM package.
That native syslog package should almost certainly have the capability to send it's messages (or generally any you might want to specify) to a remote server. I would configure that to push out to a remote server of your choice and do any parsing, filtering, or manipulating server-side. That way you don't have to worry about keeping a package up to date, or ensuring you have a system/application specific configuration. The generic config you'll end up with can, in theory, be applied to anything running linux.
Hope this helps.