forked from archiver_config/sf_databuffer
193 lines
7.4 KiB
YAML
193 lines
7.4 KiB
YAML
###################### Journalbeat Configuration Example #########################
|
|
|
|
# This file is an example configuration file highlighting only the most common
|
|
# options. The journalbeat.reference.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/journalbeat/index.html
|
|
|
|
# For more available modules and options, please see the journalbeat.reference.yml sample
|
|
# configuration file.
|
|
|
|
#=========================== Journalbeat inputs =============================
|
|
|
|
journalbeat.inputs:
|
|
# Paths that should be crawled and fetched. Possible values files and directories.
|
|
# When setting a directory, all journals under it are merged.
|
|
# When empty starts to read from local journal.
|
|
- paths: []
|
|
|
|
# The number of seconds to wait before trying to read again from journals.
|
|
#backoff: 1s
|
|
# The maximum number of seconds to wait before attempting to read again from journals.
|
|
#max_backoff: 20s
|
|
|
|
# Position to start reading from journal. Valid values: head, tail, cursor
|
|
seek: cursor
|
|
# Fallback position if no cursor data is available.
|
|
#cursor_seek_fallback: head
|
|
|
|
# Exact matching for field values of events.
|
|
# Matching for nginx entries: "systemd.unit=nginx"
|
|
#include_matches: []
|
|
include_matches:
|
|
- "systemd.unit=daq-dispatcher-node.service"
|
|
- "systemd.unit=daq-query-node.service"
|
|
- "systemd.unit=imageapi.service"
|
|
|
|
# Optional fields that you can specify to add additional information to the
|
|
# output. Fields can be scalar values, arrays, dictionaries, or any nested
|
|
# combination of these.
|
|
#fields:
|
|
# env: staging
|
|
|
|
|
|
#========================= Journalbeat global options ============================
|
|
#journalbeat:
|
|
# Name of the registry file. If a relative path is used, it is considered relative to the
|
|
# data path.
|
|
#registry_file: registry
|
|
|
|
#==================== Elasticsearch template setting ==========================
|
|
setup.template.settings:
|
|
index.number_of_shards: 1
|
|
#index.codec: best_compression
|
|
#_source.enabled: false
|
|
|
|
#================================ 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
|
|
|
|
|
|
#============================== Dashboards =====================================
|
|
# These settings control loading the sample dashboards to the Kibana index. Loading
|
|
# the dashboards is disabled by default and can be enabled either by setting the
|
|
# options here or by using the `setup` command.
|
|
#setup.dashboards.enabled: false
|
|
|
|
# The URL from where to download the dashboards archive. By default this URL
|
|
# has a value which is computed based on the Beat name and version. For released
|
|
# versions, this URL points to the dashboard archive on the artifacts.elastic.co
|
|
# website.
|
|
#setup.dashboards.url:
|
|
|
|
#============================== Kibana =====================================
|
|
|
|
# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
|
|
# This requires a Kibana endpoint configuration.
|
|
setup.kibana:
|
|
|
|
# Kibana Host
|
|
# Scheme and port can be left out and will be set to the default (http and 5601)
|
|
# In case you specify and additional path, the scheme is required: http://localhost:5601/path
|
|
# IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
|
|
host: "https://realstuff.psi.ch:5601"
|
|
ssl.certificate_authorities: ["/etc/pki/tls/certs/elastic-stack-ca.pem"]
|
|
|
|
# Kibana Space ID
|
|
# ID of the Kibana Space into which the dashboards should be loaded. By default,
|
|
# the Default Space will be used.
|
|
#space.id:
|
|
|
|
#============================= Elastic Cloud ==================================
|
|
|
|
# These settings simplify using Journalbeat with the Elastic Cloud (https://cloud.elastic.co/).
|
|
|
|
# The cloud.id setting overwrites the `output.elasticsearch.hosts` and
|
|
# `setup.kibana.host` options.
|
|
# You can find the `cloud.id` in the Elastic Cloud web UI.
|
|
#cloud.id:
|
|
|
|
# The cloud.auth setting overwrites the `output.elasticsearch.username` and
|
|
# `output.elasticsearch.password` settings. The format is `<user>:<pass>`.
|
|
#cloud.auth:
|
|
|
|
#================================ Outputs =====================================
|
|
|
|
# Configure what output to use when sending the data collected by the beat.
|
|
|
|
#-------------------------- Elasticsearch output ------------------------------
|
|
output.elasticsearch:
|
|
# Array of hosts to connect to.
|
|
hosts: ["realstuff.psi.ch:9200"]
|
|
pipeline: "imagebuffer-log-pipeline"
|
|
|
|
# Optional protocol and basic auth credentials.
|
|
protocol: "https"
|
|
username: "beats_user"
|
|
password: "beats123"
|
|
ssl.certificate_authorities: ["/etc/pki/tls/certs/elastic-stack-ca.pem"]
|
|
|
|
#----------------------------- Logstash output --------------------------------
|
|
#output.logstash:
|
|
# The Logstash hosts
|
|
#hosts: ["localhost:5044"]
|
|
|
|
# Optional SSL. By default is off.
|
|
# List of root certificates for HTTPS server verifications
|
|
#ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
|
|
|
|
# Certificate for SSL client authentication
|
|
#ssl.certificate: "/etc/pki/client/cert.pem"
|
|
|
|
# Client Certificate Key
|
|
#ssl.key: "/etc/pki/client/cert.key"
|
|
|
|
#================================ Processors =====================================
|
|
|
|
# Configure processors to enhance or manipulate events generated by the beat.
|
|
|
|
processors:
|
|
- add_host_metadata: ~
|
|
- add_cloud_metadata: ~
|
|
|
|
#================================ Logging =====================================
|
|
|
|
# Sets log level. The default log level is info.
|
|
# Available log levels are: error, warning, info, debug
|
|
#logging.level: debug
|
|
|
|
# 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: ["*"]
|
|
|
|
#============================== Xpack Monitoring ===============================
|
|
# journalbeat can export internal metrics to a central Elasticsearch monitoring
|
|
# cluster. This requires xpack monitoring to be enabled in Elasticsearch. The
|
|
# reporting is disabled by default.
|
|
|
|
# Set to true to enable the monitoring reporter.
|
|
monitoring.enabled: true
|
|
|
|
# Sets the UUID of the Elasticsearch cluster under which monitoring data for this
|
|
# Journalbeat instance will appear in the Stack Monitoring UI. If output.elasticsearch
|
|
# is enabled, the UUID is derived from the Elasticsearch cluster referenced by output.elasticsearch.
|
|
monitoring.cluster_uuid: "57-GhvUVR1WM1D-42XEFYg"
|
|
|
|
# Uncomment to send the metrics to Elasticsearch. Most settings from the
|
|
# Elasticsearch output are accepted here as well.
|
|
# Note that the settings should point to your Elasticsearch *monitoring* cluster.
|
|
# Any setting that is not set is automatically inherited from the Elasticsearch
|
|
# output configuration, so if you have the Elasticsearch output configured such
|
|
# that it is pointing to your Elasticsearch monitoring cluster, you can simply
|
|
# uncomment the following line.
|
|
#monitoring.elasticsearch:
|
|
|
|
#================================= Migration ==================================
|
|
|
|
# This allows to enable 6.7 migration aliases
|
|
#migration.6_to_7.enabled: true
|