8 ms·
SYSLOG! For the love of god, please support syslog! I work as a consultant supporting a SIEM, and the amount of hoops we need to jump through to get logs from W
by freehunter 11y ago
SYSLOG! For the love of god, please support syslog! I work as a consultant supporting a SIEM, and the amount of hoops we need to jump through to get logs from Windows servers is crazy compared to changing one line in a syslog.conf file. I actually dread when a client says "we're an all Windows environment" because wow initial setup just got that much harder.
And if we want to install a syslog forwarder on their domain controllers... no one ever trusts software installed on their domain controllers. Everyone trusts a single line in syslog.conf.
- darklajid 11y agoYou CAN export the event log data of course, even remotely. But it's rather ugly and I agree that some standard aggregation (syslog or anything) would be great.
- mhurron 11y agoEven the choice of outputs (of which remote syslog should be one) would be a great addition to the Windows event log.
- sudioStudio64 11y agoMicrosoft has supported event forwarding since 2003. You can set the machines to push events or have them pulled.
- hamburglar 11y agoHilarious thought: how much stuff like syslog support would microsoft have to add to start attracting systemd refugees? :D
- sudioStudio64 11y agoMS has supported event forwarding since 2003. You can set machines to forward events or have them pulled. The events are XML that conform to a published schema. There is a WMI call that call pull the aggregated events off the collection servers. I heard this kind of thing from a vendor the other day. It's like people don't even try to learn how it works. Why are they different? The event log has some transactional guarantees that were required for a specific kind of security evaluation...C2? I can't remember the rest. The thing is...you don't have to install a client on the domain controllers. You can setup forwarding to some log hosts and collect them there.
- pjc50 11y agoIt's like people don't even try to learn how it works It's much harder to know how it works, for some reason. Information like this doesn't make its way into the community and circulate. On a UNIX system you can poke around /etc and get an idea of the scope of what is configurable. The same is very much not true of the registry and only slightly true of WMI.
- sudioStudio64 11y agoYou are right. The guy that wrote PowerShell says that UNIX is document oriented configuration while windows is API oriented configuration. To get into it in any depth you have to approach windows programmatically. The most power is through C\C++...to be a good windows admin you need to read the docs about how you interact with different subsystems, even if you aren't going to code against them.
- lygaret 11y agoThat's a really good point, thank you. I've never really thought about it that way; e.g. the registry is something you should sort of treat as an opaque blob of state (like a smalltalk image?) that you just mutate over time programatically, rather than as a declarative set of configurations to bring the machine to at any time.
- silon3 11y ago> You are right. The guy that wrote PowerShell says that UNIX is document oriented configuration while windows is API oriented configuration. That's an interesting way of putting it. I strongly prefer the Unix way then,(just avoid turing complete config languages).
- sudioStudio64 11y agoAfter coding for several years, the two aren't all that different. I'm not saying that I think that the UNIX WAY is ever going to go away...but I do think that extreme scale makes the programmatic approach to configuration make more sense. Instead of treating every system as a "system" you treat it as a simple programmable node among thousands of others. You are already starting to see Linux go this way with systemD. The stuff that the CoreOS people are doing with etcD, fleet, and flannel are really the future of *NIX. Please cut me some slack...I'm NOT TRYING TO ARGUE ABOUT SYSTEMD. I'm just saying that it's oriented towards developers using API's. That's one of the reasons why admins who are used to the "one true way" dislike it so much. And they should have options if they don't want to use it. I'm just saying that cloud scale deployments are driving changes to infrastructure to make it more "programmable". I'm not even saying it's "right"...Its just a observation.