aboutsummaryrefslogtreecommitdiff
path: root/ansible/roles/kibana
AgeCommit message (Collapse)AuthorFilesLines
2016-11-15Remove Ansible from KollaSteven Dake12-163/+0
Change-Id: I5396e4b9927d3e65b6aa4185238a43a4765a996b
2016-11-08Add kolla_logs volume to kibana containerChristian Berendt1-0/+1
Change-Id: Ie3a04fa6c0f7406fcbc9033a38d9941509d9dc90 Closes-bug: #1640303
2016-11-03Move precheck into its own roleJeffrey Zhang1-0/+1
* Merge prechecks.yml and site.yml playbook * Create empty precheck.yml into all roles. Change-Id: I8a138558a26c0a2a66c5fd48ed37be657c99c1dd Implements: blueprint condition-pre-check
2016-11-01Merge "Configure log path for kibana"Jenkins1-0/+1
2016-11-01added kibana reconfigureprameswar1-0/+63
Closes-bug: #1636806 Change-Id: I24e5d40ea590212114611da77cf0dfd145b76100
2016-10-24Configure log path for kibanaJeffrey Zhang1-0/+1
Closes-Bug: #1635989 Change-Id: I99402e54e7cc2f1ad972021bb1056966f5c08bff
2016-10-10Add upgrade tasks for KibanaChristian Berendt1-0/+3
Change-Id: I860fdc3268d0fdcb775ea345bb0eb621c8dafe07 Closes-bug: #1631902
2016-09-23ES and Kibana config modification for KubeSerguei Bezverkhi1-2/+2
This PS modifies Elasticsearch and Kibana configuration templates so genconfig can genarate Kubernetes compatible config for these services. TrivialFix Change-Id: I6886307a163a9ca27a29e6dbdac4f9080948e4b5
2016-09-21Add "---" into some files of yamlcaoyuan1-0/+1
TrivialFix Change-Id: Id2cd736f136068514f26977b434b15a8b1ffc8be
2016-05-03map the host localtime to the containerJeffrey Zhang1-0/+1
Closes-Bug: #1577148 Change-Id: I636cefc63cf532434a41af3898b63dffa711e280
2016-03-05Make Heka send logs to ElasticsearchÉric Lemoine2-20/+11
This patch includes changes relative to integrating Heka with Elasticsearch and Kibana. The main change is the addition of an Heka ElasticSearchOutput plugin to make Heka send the logs it collects to Elasticsearch. Since Logstash is not used the enable_elk deploy variable is renamed to enable_central_logging. If enable_central_logging is false then Elasticsearch and Kibana are not started, and Heka won't attempt to send logs to Elasticsearch. By default enable_central_logging is set to false. If enable_central_logging is set to true after deployment then the Heka container needs to be recreated (for Heka to get the new configuration). The Kibana configuration used property names that are deprecated in Kibana 4.2. This is changed to use non-deprecated property names. Previously logs read from files and from Syslog had a different Type in Heka. This is changed to always use "log" for the Type. In this way just one index instead of two is used in Elasticsearch, making things easier to the user on the visualization side. The HAProxy configuration is changed to add entries for Kibana. Kibana server is now accessible via the internal VIP, and also via the external VIP if there's one configured. The HAProxy configuration is changed to add an entry for Elasticsearch. So Elasticsearch is now accessible via the internal VIP. Heka uses that channel for communicating with Elasticsearch. Note that currently the Heka logs include "Plugin elasticsearch_output" errors when Heka starts. This occurs when Heka starts processing logs while Elasticsearch is not yet started. These are transient errors that go away when Elasticsearch is ready. And with buffering enabled on the ElasticSearchOuput plugin logs will be buffered and then retransmitted when Elasticsearch is ready. Change-Id: I6ff7a4f0ad04c4c666e174693a35ff49914280bb Implements: blueprint central-logging-service
2016-02-26Change kolla_internal_address variableSamYaple2-2/+2
Due to poor planning on our variable names we have a situation where we have "internal_address" which must be a VIP, but "external_address" which should be a DNS name. Now with two vips "external_vip_address" is a new variable. This corrects that issue by deprecating kolla_internal_address and replacing it with 4 nicely named variables. kolla_internal_vip_address kolla_internal_fqdn kolla_external_vip_address kolla_external_fqdn The default behaviour will remain the same, and the way the variable inheritance is setup the kolla_internal_address variable can still be set in globals.yml and propogate out to these 4 new variables like it normally would, but all reference to kolla_internal_address has been completely removed. Change-Id: I4556dcdbf4d91a8d2751981ef9c64bad44a719e5 Partially-Implements: blueprint ssl-kolla
2016-02-25Add the default empty reconfigure.yml file to all rolesJeffrey Zhang1-0/+1
DocImpact Partially-implements: bp kolla-reconfig Change-Id: I9738e80960bcfbef18d1ef1b7942f81c45684e85
2016-02-15Use variables to specify http or https when constructing URLsDave McCowan1-1/+1
To allow for TLS to protect the service endpoints, the protocol in the URLs for the endpoints will be either http or https. This patch removes the hardcoded values of http and replaces them with variables that can be adjusted accordingly in future patches. Change-Id: Ibca6f8aac09c65115d1ac9957410e7f81ac7671e Partially-implements: blueprint ssl-kolla
2016-02-09Add missing upgrade stubs for kibana/mongodbPaul Bourke1-0/+1
TrivialFix Co-Authored-By: Ryan Hallisey <rhallise@redhat.com> Change-Id: Ia83f642d3817116e2ba99285efc12b583f07bbd1
2016-01-26Added Kibana and its deployment.akwasniewska9-0/+99
Part of ELK stack. Includes Dockerfiles for both Centos and Ubuntu. Change-Id: I1d955a5c51e416cc572eb2c9b4c57982a1d6ab67 Partially-implements: blueprint central-logging-service
generated by cgit v1.2.3 (git 2.39.1) at 2026-11-11 22:23:44 +0000