Winlogbeat logging.level does not level properly


(mbk) #1

Hello everyone,

i’ve set logging.level to warning. So this should only collect events with level = critical, error, warning.

But i am still receiving a massive amount of Information messages. I already restarted the service, but its not stopping.

Did i miss something?

Here my winlogbeat.yml

###################### Winlogbeat Configuration Example ##########################

# This file is an example configuration file highlighting only the most common
# options. The winlogbeat.full.yml file from the same directory contains all the
# supported options with more comments. You can use it as a reference.
#
# You can find the full configuration reference here:
# https://www.elastic.co/guide/en/beats/winlogbeat/index.html

#======================= Winlogbeat specific options ==========================

# event_logs specifies a list of event logs to monitor as well as any
# accompanying options. The YAML data type of event_logs is a list of
# dictionaries.
#
# The supported keys are name (required), tags, fields, fields_under_root,
# forwarded, ignore_older, level, event_id, provider, and include_xml. Please
# visit the documentation for the complete details of each option.
# https://go.es.io/WinlogbeatConfig
winlogbeat.event_logs:
  - name: Application
ignore_older: 160h
# - name: Security
  - name: System
  - name: Antivirus
  - name: HardwareEvents
  - name: Internet Explorer
  - name: Kaspersky Event Log
  - name: Kaspersky Security
  - name: Microsoft-Windows-All-User-Install-Agent/Admin
  - name: Microsoft-Windows-AppHost/Admin
  - name: Microsoft-Windows-Application Server-Applications/Admin
  - name: Microsoft-Windows-AppModel-Runtime/Admin 
  - name: Microsoft-Windows-AppReadiness/Admin 
  - name: Microsoft-Windows-Storage-ATAPort/Admin 
  - name: Microsoft-Windows-DataIntegrityScan/Admin 
  - name: Microsoft-Windows-DataIntegrityScan/CrashRecovery 
  - name: Microsoft-Windows-DSC/Admin 
  - name: Microsoft-Windows-DeviceSetupManager/Admin 
  - name: Microsoft-Windows-Dhcp-Client/Admin 
  - name: Microsoft-Windows-DhcpNap/Admin 
  - name: Microsoft-Windows-Dhcpv6-Client/Admin 
  - name: Microsoft-Windows-Diagnosis-Scripted/Admin 
  - name: Microsoft-Windows-Storage-Disk/Admin 
  - name: Microsoft-Windows-EnrollmentPolicyWebService/Admin 
  - name: Microsoft-Windows-EnrollmentWebService/Admin 
  - name: Microsoft-Windows-FileServices-ServerManager-EventProvider/Admin 
  - name: Microsoft-Windows-GenericRoaming/Admin 
  - name: Microsoft-Windows-iSCSITarget-Service/Admin 
  - name: Microsoft-Windows-Kernel-EventTracing/Admin 
  - name: Microsoft-Management-UI/Admin 
  - name: Microsoft-Windows-MUI/Admin 
  - name: Microsoft-Windows-PowerShell/Admin 
  - name: Microsoft-Windows-PrintService/Admin 
  - name: Microsoft-Windows-PushNotification-Platform/Admin 
  - name: Microsoft-Rdms-UI/Admin 
  - name: Microsoft-Windows-RemoteApp and Desktop Connections/Admin 
  - name: Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Admin 
  - name: Microsoft-Windows-ServerManager-MultiMachine/Admin 
  - name: Microsoft-Windows-SmartCard-TPM-VCard-Module/Admin 
  - name: Microsoft-Windows-SMBDirect/Admin 
  - name: WitnessClientAdmin 
  - name: Microsoft-Windows-Storage-Tiering/Admin 
  - name: Microsoft-Windows-Storage-ClassPnP/Admin 
  - name: Microsoft-WS-Licensing/Admin 
  - name: Microsoft-Windows-Storage-Storport/Admin 
  - name: Microsoft-Windows-TerminalServices-ClientUSBDevices/Admin 
  - name: Microsoft-Windows-TerminalServices-LocalSessionManager/Admin 
  - name: Microsoft-Windows-TerminalServices-PnPDevices/Admin 
  - name: Microsoft-Windows-TerminalServices-Printers/Admin 
  - name: Microsoft-Windows-TerminalServices-RemoteConnectionManager/Admin 
  - name: Microsoft-Windows-TerminalServices-ServerUSBDevices/Admin 
  - name: Microsoft-Windows-TerminalServices-SessionBroker-Client/Admin 
  - name: Microsoft-Windows-VerifyHardwareSecurity/Admin 
  - name: Microsoft-Windows-Workplace Join/Admin 
  - name: Remote Lab Exchange Service 
  - name: Key Management Service 
  - name: Windows Assessment Services Client 
  - name: Windows PowerShell 
#================================ General =====================================

# The name of the shipper that publishes the network data. It can be used to group
# all the transactions sent by a single shipper in the web interface.
#name:

# The tags of the shipper are included in their own field with each
# transaction published.
#tags: ["service-X", "web-tier"]

# Optional fields that you can specify to add additional information to the
# output.
#fields:
#  env: staging

#================================ Outputs =====================================

# Configure what outputs to use when sending the data collected by the beat.
# Multiple outputs may be used.

#-------------------------- Elasticsearch output ------------------------------
#output.elasticsearch:
  # Array of hosts to connect to.
  #hosts: ["localhost:9200"]

  # Optional protocol and basic auth credentials.
  #protocol: "https"
  #username: "elastic"
  #password: "changeme"

#----------------------------- Logstash output --------------------------------
output.logstash:
  # The Logstash hosts
  hosts: ["192.168.100.180:5044"]

  # Optional SSL. By default is off.
  # List of root certificates for HTTPS server verifications
  ssl.certificate_authorities: ["/Program Files/Winlogbeat/logstash-forwarder.crt"]

  # Certificate for SSL client authentication
  #ssl.certificate: "/etc/pki/client/cert.pem"

  # Client Certificate Key
  #ssl.key: "/etc/pki/client/cert.key"

#================================ Logging =====================================

# Sets log level. The default log level is info.
# Available log levels are: critical, error, warning, info, debug
logging.level: warning

# At debug level, you can selectively enable logging only for some components.
# To enable all selectors use ["*"]. Examples of other selectors are "beat",
# "publish", "service".
#logging.selectors: ["*"]

(Andrew Kroh) #2

logging.level controls the verbosity of logging from Winlogbeat to the log file. It does not control what events are read from the Windows event logs and sent to the output (Logstash). You can use the event_logs.level option to specify what event levels you would like reported.

winlogbeat.event_logs:
  - name: Application
    ignore_older: 160h
    level: critical, error, warning
  - name: System
    ignore_older: 160h
    level: critical, error, warning
  - name: Antivirus
    ignore_older: 160h
    level: critical, error, warning

(mbk) #3

Awesome! Thank you very much for the help! I'll try that out :slight_smile:


(system) #4

This topic was automatically closed after 21 days. New replies are no longer allowed.