Skip to main content
Sumo Logic

Remote Windows Event Log Source

Set up a Remote Windows Event Log Source to use a single Sumo Logic Collector to collect Windows event log entries from multiple remote systems.

The following about setting up a Remote Windows Event Log Source:

  • Remote Windows Event Sources can only be run on, and collect remotely from, systems running Windows Server 2008 (Windows Vista) or later.
  • It isn't necessary for the remote systems to have a Sumo Logic collector installed. 
  • You can specify a comma-separated list of remote hostnames to collect from.
  • You'll need to configure a few settings to enable remote access.

To configure a remote Windows Event Log Source

  1. Complete the prerequisites for collecting remote events.
  2. In Sumo Logic select Manage Data > Collection > Collection.
  3. Find the name of the installed collector to which you'd like to add a source. Click Add and then choose Add Source from the pop-up menu.
  4. Select the Windows Event Log source.
  5. Choose Remote for Type of Windows Source.
  6. Set the following:
    • Name. Type the name you'd like to display for this source in the Sumo Logic Web Application. 
    • Description. Optional description.
    • Windows host(s). Enter one or more hostnames for the Windows machines from which you want to collect Windows Events. If you'd like to collect from more than one remote host, separate the hostnames with a comma. (If you enter more than one hostname, each host must allow event log access from the same domain user. See the prerequisites for more information.) The hostname can be a maximum of 128 characters.
      The hostname values are parsed and applied to your event logs as _sourceHost metadata automatically. The value is parsed from the field Computer in your event logs.
    • Source Category. Enter a string to tag the logs collected from this Source with searchable metadata. For example, typing web_apps tags all the logs from this Source in the sourceCategory field. For more information, see Metadata Naming Conventions and our Best Practices: Good Source Category, Bad Source Category.
      You can define a Source Category value using system environment variables, see Configuring sourceCategory using variables below.
    • Fields. Click the +Add Field link to add custom log metadata Fields.
      • Define the fields you want to associate, each field needs a name (key) and value. 
        • green check circle.png A green circle with a check mark is shown when the field exists and is enabled in the Fields table schema.
        • orange exclamation point.png An orange triangle with an exclamation point is shown when the field doesn't exist, or is disabled, in the Fields table schema. In this case, an option to automatically add or enable the nonexistent fields to the Fields table schema is provided. If a field is sent to Sumo that does not exist in the Fields schema or is disabled it is ignored, known as dropped.
    • Windows Domain. Type the name of the Windows domain, the username for this host, and the password.
    • Windows Event Types. Select the event types you want to collect:
      • Standard Event Channels. Select the main check box for all types, or individual check boxes for specific types (Security, Application, and/or System).
      • Custom Event Channels to specify, in a comma-separated list, the channels you'd like to collect from. If you need help finding channels on the machine where the Source is installed, see Windows Event Source Custom Channels

      windows_file_source_event_types.png

    • Metadata. Choose whether you would like the collector to minimize the amount of data collected by omitting the full message text of each event. Core metadata fields such as event ID, timestamp, user name, as well as the unformatted event data will still be present. This can reduce data usage and increase event throughput, but will prevent many dashboards and apps from correctly extracting data.

      Metadata options

    • Collection should begin. Choose or enter how far back you'd like to begin collecting historical logs. You can either:
      • Choose a predefined value from dropdown list, ranging from “Now” to “24 hours ago” to “All Time”, or
      • Enter a relative value. To enter a relative value, click the Collection should begin field and press the delete key on your keyboard to clear the field. Then, enter a relative time expression, for example “-1w”. You can define when you want collection to begin in terms of months (M), weeks (w), days (d), hours (h) and minutes (m).
    • Security Identifier. Newer collectors can map security identifiers (SIDs) to usernames. Choose:
      • Both Security Identifier and Username
      • Security Identifier Only
      • Username Only
    • Create any Processing Rules you'd like for the new source.
  7. Click Save.

You can return to this dialog and edit the settings for the source at any time.

Configuring sourceCategory using variables

Collector versions 19.216-22 and later allow you to define Source Category and Source Host metadata values with system environment variables from the host machine.

When configuring your Source, specify the system environment variables by prepending sys. and wrapping them in double curly brackets {{}} in this form:

{{sys.VAR_NAME}}

Where VAR_NAME is an environment variable name, for example:

{{sys.PATH}}

You can use multiple variables, for example:

{{sys.PATH}}-{{sys.YourEnvVar}}

environment variable usage.png

You can incorporate text in the metadata expression, for example:

AnyTextYouWant_{{sys.PATH}}_{{sys.YourEnvVar}}

If a user-defined variable doesn’t exist, that portion of the metadata field will be blank.