This functionality is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.
This is a module for Zoom webhook logs. The module creates an HTTP listener that accepts incoming webhooks from Zoom.
To configure Zoom to send webhooks to the filebeat module, please follow the Zoom Documentation.
Read the quick start to learn how to configure and run modules.
Configure the moduleedit
You can further refine the behavior of the
zoom module by specifying
variable settings in the
modules.d/zoom.yml file, or overriding settings at the command line.
Each fileset has separate variable settings for configuring the behavior of the
module. If you don’t specify variable settings, the
zoom module uses
For advanced use cases, you can also override input settings. See Override input settings.
When you specify a setting at the command line, remember to prefix the
setting with the module name, for example,
webhook fileset settingsedit
When a webhook integration is created on Zoom, it will show a special token used to ensure that filebeat only handles HTTP requests from the correct source.
This is configured with the
secret.value settings as shown below.
- module: zoom webhook: enabled: true var.input: http_endpoint var.listen_address: 0.0.0.0 var.listen_port: 8080 var.secret.header: Authorization var.secret.value: ZOOMTOKEN
An array of glob-based paths that specify where to look for the log files. All
patterns supported by Go Glob
are also supported here. For example, you can use wildcards to fetch all files
from a predefined level of subdirectories:
/path/to/log/*/*.log. This fetches all
.logfiles from the subfolders of
/path/to/log. It does not fetch log files from the
/path/to/logfolder itself. If this setting is left empty, Filebeat will choose log paths based on your operating system.
- The IP address of the interface the module should listen on. Also supports 0.0.0.0 to listen on all interfaces.
- The port the module should be listening on.
- Configuration options for SSL parameters like the SSL certificate and CA to use for the HTTP(s) listener See SSL for more information.
For a description of each field in the module, see the exported fields section.
Intro to Kibana
ELK for Logs & Metrics