e013623e78
Right now all roles assume that kibana has been deployed using the stack and `kibana` group is defined in Ansible. However if one need just to use journalbeat or filebeat roles to push data to external Kibana - it's barely possible. Defining `kibana` group is risky as open doors for installKibana playbook execution. This patch adds variable kibana_target along with more role-specific variables that allow to adjust thi behaviour and manually supply Kibana endpoint to be configured. Change-Id: Id2a42ae9c6146dcc9e86b15fee36372b95461d20
23 lines
808 B
YAML
23 lines
808 B
YAML
---
|
|
# Copyright 2018, Rackspace US, Inc.
|
|
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
# you may not use this file except in compliance with the License.
|
|
# You may obtain a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS,
|
|
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
# See the License for the specific language governing permissions and
|
|
# limitations under the License.
|
|
|
|
# APM vars
|
|
apm_interface: 0.0.0.0
|
|
apm_port: 8200
|
|
apm_token: SuperSecrete
|
|
# Manually define Kibana targets.
|
|
# Default: hosts from Ansible `kibana` group will be used
|
|
apm_kibana_target: "{{ kibana_target | default('') }}"
|