Has anyone had any success sending a test message to a beats input to emulate a windows message coming in? (preferably via powershell) Once again my google-fu is failing. Example meta-code:
$> netcat-send-message -message "This is my test message" -server graylogOne:5044
netcat-send-message is not a real command I am making the whole thing up… hoping its a simple command like this.
I should have put in there that I am writing a Powershell script to test out windows event_ID’s and their alerts - I just need a command to insert a test event into winlogbeat with the relevant event_id’s.
I am debating just creating a filebeat instance on a test machine and dumping one-liners to be caught in there…if I process each line to include event_ID field and any other relevant information I can adjust the input and pipelines to consider data coming from filebeat as well… It’s not a pretty situation though - I would prefer to create a powershell script that perhaps asks for your API_KEY and a server to shunt messages to for testing. Originally I was creating powershell commands that would actively change AD but that is riskier… better to just push a message into Graylog somehow that looks like a security message from Windows and sets off the alert for testing…
I might have to ask for some developer help… What IS that Beats input expecting to see so it can do it’s magic!?!
I can make it a filebeat on whatever machine I am testing from, then use Powershell to just insert a message line to the text file - that way I can manage powershell permissions across the testing environment and it will come in on the same input–>stream.