-
Notifications
You must be signed in to change notification settings - Fork 68
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #18 from andrewvc/mock-k8s
Add mock k8s config
- Loading branch information
Showing
1 changed file
with
226 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,226 @@ | ||
################### Heartbeat Configuration Example ######################### | ||
|
||
# This file is an example configuration file highlighting only some common options. | ||
# The heartbeat.reference.yml file in the same directory contains all the supported options | ||
# with detailed comments. You can use it for reference. | ||
# | ||
# You can find the full configuration reference here: | ||
# https://www.elastic.co/guide/en/beats/heartbeat/index.html | ||
|
||
############################# Heartbeat ###################################### | ||
|
||
# Define a directory to load monitor definitions from. Definitions take the form | ||
# of individual yaml files. | ||
heartbeat.config.monitors: | ||
# Directory + glob pattern to search for configuration files | ||
path: ${path.config}/monitors.d/*.yml | ||
# If enabled, heartbeat will periodically check the config.monitors path for changes | ||
reload.enabled: false | ||
# How often to check for changes | ||
reload.period: 5s | ||
|
||
# Configure monitors inline | ||
heartbeat.monitors: | ||
- type: tcp | ||
id: redis | ||
name: Redis | ||
hosts: ["localhost:6379"] | ||
schedule: '@every 10s' | ||
processors: | ||
- add_fields: | ||
target: kubernetes | ||
fields: | ||
container: | ||
id: 4f79ebad-e2b3-46ab-abba-bc00dda090c7 | ||
image: custom-redis | ||
name: custom-redis | ||
node: | ||
name: demo | ||
pod: | ||
name: custom-redis | ||
uid: 5f75eba1-e2b3-46ab-abba-bc00dda090c1 | ||
- type: tcp | ||
hosts: ["localhost:5601"] | ||
schedule: '@every 10s' | ||
id: kbn | ||
name: Kibana | ||
processors: | ||
- add_fields: | ||
target: kubernetes | ||
fields: | ||
container: | ||
id: 4f79ebad-e2b3-46ab-abba-bc00dda090c7 | ||
image: custom-redis | ||
name: custom-redis | ||
node: | ||
name: demo | ||
pod: | ||
name: custom-redis | ||
uid: 5f75eba1-e2b3-46ab-abba-bc00dda090c1 | ||
- type: tcp | ||
hosts: ["localhost:9200"] | ||
schedule: '@every 10s' | ||
id: es | ||
name: Elasticsearch | ||
processors: | ||
- add_fields: | ||
target: kubernetes | ||
fields: | ||
container: | ||
id: 4f79ebad-e2b3-46ab-abba-bc00dda090c7 | ||
image: custom-redis | ||
name: custom-redis | ||
node: | ||
name: demo | ||
pod: | ||
name: custom-redis | ||
uid: 5f75eba1-e2b3-46ab-abba-bc00dda090c1 | ||
- type: http | ||
hosts: ["localhost:5678"] | ||
schedule: '@every 10s' | ||
id: pet-clinic | ||
name: Pet Clinic | ||
processors: | ||
- add_fields: | ||
target: kubernetes | ||
fields: | ||
container: | ||
id: 4f79ebad-e2b3-46ab-abba-bc00dda090c7 | ||
image: custom-redis | ||
name: custom-redis | ||
node: | ||
name: demo | ||
pod: | ||
name: custom-redis | ||
uid: 5f75eba1-e2b3-46ab-abba-bc00dda090c1 | ||
|
||
|
||
# Total test connection and data exchange timeout | ||
#timeout: 16s | ||
|
||
#==================== 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 | ||
|
||
|
||
#============================== 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: "localhost:5601" | ||
|
||
# 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 Heartbeat 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: ["localhost:9200"] | ||
|
||
# Optional protocol and basic auth credentials. | ||
#protocol: "https" | ||
#username: "elastic" | ||
#password: "changeme" | ||
|
||
#----------------------------- 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 ===================================== | ||
|
||
processors: | ||
- add_observer_metadata: | ||
geo: | ||
name: us-midwest-dc | ||
|
||
#================================ 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: ["*"] | ||
|
||
#============================== X-Pack Monitoring =============================== | ||
# heartbeat 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: false | ||
|
||
# Sets the UUID of the Elasticsearch cluster under which monitoring data for this | ||
# Heartbeat 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: | ||
|
||
# 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 |