Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct syntax for adding events? #11

Open
tomg1983 opened this issue Mar 7, 2018 · 3 comments
Open

Correct syntax for adding events? #11

tomg1983 opened this issue Mar 7, 2018 · 3 comments

Comments

@tomg1983
Copy link

tomg1983 commented Mar 7, 2018

What's the correct syntax for adding multiple event logs? So far, I only managed to add one like this:

    event_logs => {
        'options' => {
            'name' => 'Application',
            'ignore_older' => '72h',
        }
    },

thx!

@edestecd
Copy link
Contributor

edestecd commented Mar 9, 2018

$event_logs = {
    'Security' => {
      'tags' => ['secure'],
    },
    'Another' => {
      'tags' => ['another'],
   }
  }

@f1ngerscr0ssed
Copy link

An example I have used:

$events = "4733, 4732, 1102, 4624, 4625, 4647"

class { 'winlogbeat':
  outputs => {
    'logstash'     => {
              'hosts' =>  [
                          'targethost:6655'
                          ],
              'ssl' => {
              'certificate'  => $puppet_cert_path,
              'key'          => $puppet_key_path, 
              },
           #   'index'            => 'winlogbeat',
         
          },
              },
event_logs => {
        
            'Security' => {
            'event_id' => $events, 
            'ignore_older' => '1h',
            },
 },
}

You have to fit all the event IDs inside a string,

Cheers!

@nsticco
Copy link

nsticco commented Mar 28, 2019

Would it be alright if I created a PR to add this to the documentation?

I assumed that it would be nested inside a winlogbeat property based on the official Elastic winlogbeat.yml example, but it looks like it's being nested in this automatically by the config.pp code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants