summaryrefslogtreecommitdiffstats
path: root/roles/openshift_logging_fluentd
Commit message (Collapse)AuthorAgeFilesLines
* Relocate filter plugins to lib_utilsMichael Gugino2017-12-182-1/+2
| | | | | | | | | | | | | | This commit relocates filter_plugings to lib_utils, changes the namespacing to prevent unintended use of older versions that may be present in filter_plugins/ directory on existing installs. Add lib_utils to meta depends for roles Also consolidate some plugins into lib_utils from various other areas. Update rpm spec, obsolete plugin rpms.
* openshift_logging_{fluentd,mux}_file_buffer_limit mismatchNoriko Hosoi2017-12-141-1/+1
| | | | | . fixing a typo in fluentd template . adjusting the default value of openshift_logging_mux_file_buffer_limit
* Merge pull request #6369 from irozzo-1A/logging-becomeRussell Teague2017-12-131-0/+1
|\ | | | | Do not escalate privileges in logging stack deployment task
| * Do not escalate privileges in logging stack deployment taskirozzo2017-12-051-0/+1
| |
* | Include Deprecation: Convert to include_tasksRussell Teague2017-12-061-2/+2
| |
* | Fix hosted varsMichael Gugino2017-12-051-0/+1
|/ | | | | | Remove hosted vars from openshift_facts. The current pattern is causing a bunch of undesired sideffects.
* Merge pull request #5652 from ruromero/bz1498398OpenShift Merge Robot2017-11-181-0/+2
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue. Add enclosing <store> tags to sample secure-forward.conf files This fixes [BZ#1498398](https://bugzilla.redhat.com/show_bug.cgi?id=1498398) The examples provided in the documentation to configure the secure forward mention the configuration must be enclosed between the <store> tag. For that I think the examples should include it as well. See [3.6 Documentation](https://docs.openshift.com/container-platform/3.6/install_config/aggregate_logging.html#aggregated-fluentd) ~~~ <store> @type secure_forward self_hostname pod-${HOSTNAME} shared_key thisisasharedkey secure yes enable_strict_verification yes ca_cert_path /etc/fluent/keys/your_ca_cert ca_private_key_path /etc/fluent/keys/your_private_key ca_private_key_passphrase passphrase <server> host ose1.example.com port 24284 </server> <server> host ose2.example.com port 24284 standby </server> <server> host ose3.example.com port 24284 standby </server> </store> ~~~
| * bug 1498398. Enclose content between store tagRuben Romero Montes2017-10-041-0/+2
| |
* | Addressing tox errorsEric Wolinetz2017-11-071-8/+8
| |
* | Updating logging components image defaulting pattern to match ↵Eric Wolinetz2017-11-065-7/+24
| | | | | | | | openshift_logging pattern
* | bug 1506073. Lower cpu request for logging when it exceeds limitJeff Cantrill2017-10-271-2/+1
| |
* | Bug 1452939 - change Logging & Metrics imagePullPolicyJan Wozniak2017-10-231-1/+1
| | | | | | | | | | - all images logging and metrics change their default imagePullPolicy from Always to IfNotPresent
* | Use "requests" for CPU resources instead of limitsPeter Portante2017-10-193-6/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We now use a CPU request to ensure logging infrastructure pods are not capped by default for CPU usage. It is still important to ensure we have a minimum amount of CPU. We keep the use of the variables *_cpu_limit so that the existing behavior is maintained. Note that we don't want to cap an infra pod's CPU usage by default, since we want to be able to use the necessary resources to complete it's tasks. Bug 1501960 (https://bugzilla.redhat.com/show_bug.cgi?id=1501960)
* | Add switch to enable/disable container engine's audit log being stored in ES.Josef Karasek2017-10-113-1/+29
| | | | | | | | If enabled, tho logs are stored in ES' operations index, accesible only by cluster admins.
* | Bug 1490647 - logging-fluentd deployed with openshift_logging_use_mux=false ↵Noriko Hosoi2017-10-101-3/+9
|/ | | | | | | | fails to start due to missing If openshift_logging_use_mux=False and openshift_logging_mux_allow_external=False, then all other mux related parameters should be set to False (if boolean) or removed (e.g. openshift_logging_mux_client_mode should be undefined).
* minor update to README and removed dead filestran2017-09-271-209/+0
|
* Added new variables for logging role for remote-syslog pluginstran2017-09-272-0/+255
| | | | | | | | Includes the following code review fixes, and a rebase with upstream/master - mux.j2 template needed mux specific parameters for syslog configs - fixed bug in IF condition not checking for true-ness - updated README wording to remove ambiguity of payload_key's datatype
* Merge pull request #4973 from wozniakjan/logging_eventrouterOpenShift Merge Robot2017-09-271-0/+4
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Automatic merge from submit-queue logging: introducing event router Initial concept integrating kubernetes events to EFK stack using [eventrouter](https://github.com/heptio/eventrouter) - **eventrouter** is deployed to logging project, has a service account and its own role to read events - **eventrouter** watches kubernetes events, marshalls them to JSON and outputs to its STDOUT - **fluentd** picks them up and inserts to elastic search logging project index Kubernetes events could be easily stored into different index. Among other ways, it could be achieved either by a fluentd filter plugin or custom eventrouter sink. Pending actions: - [x] - get our downstream and upstream images for eventrouter, don't use heptio's cc: @josefkarasek , @jcantrill , @richm
| * logging: introducing event routerJan Wozniak2017-09-261-0/+4
| | | | | | | | | | | | | | | | - eventrouter has its own role 'openshift_logging_eventrouter' written as a template - 'openshift_logging_install_eventrouter' controls whether it gets included in the playbook or not - deployed by default to 'default' namespace
* | Merge pull request #5503 from nhosoi/output_config_testOpenShift Merge Robot2017-09-261-0/+2
|\ \ | | | | | | | | | | | | Automatic merge from submit-queue Fluentd: one output tag, one output plugin (origin-aggregated-logging)
| * | Fluentd: one output tag, one output pluginNoriko Hosoi2017-09-251-0/+2
| |/ | | | | | | Adding <label @OUTPUT> to fluent.conf.
* | Remove logging ES_COPY featureJeff Cantrill2017-09-223-4/+3
|/
* Merge pull request #5289 from jcantrill/1487573_fix_allowed_es_versionOpenShift Bot2017-09-081-2/+2
|\ | | | | Merged by openshift-bot
| * bug 1487573. Bump the allowed ES versionsJeff Cantrill2017-09-011-2/+2
| |
* | logging set memory request to limitJeff Cantrill2017-08-301-0/+2
|/
* Revert "logging set memory request to limit"Scott Dodson2017-08-291-2/+0
|
* Merge pull request #5119 from jcantrill/logging_memory_same_as_limitScott Dodson2017-08-291-0/+2
|\ | | | | logging set memory request to limit
| * logging set memory request to limitJeff Cantrill2017-08-231-0/+2
| |
* | Merge pull request #5044 from wozniakjan/logging_role_based_image_versionsOpenShift Bot2017-08-252-3/+3
|\ \ | |/ |/| Merged by openshift-bot
| * Bug 1471322: logging roles based image versionsJan Wozniak2017-08-182-3/+3
| | | | | | | | | | | | Allowing to specify an image version for each logging component https://bugzilla.redhat.com/show_bug.cgi?id=1471322
* | Fix syntax for when statementRodolfo Carvalho2017-08-101-1/+1
|/ | | | | | | | Without that, playbook runs print warnings such as this: [WARNING]: when statements should not include jinja2 templating delimiters such as {{ }} or {% %}. Found: {{ g_etcd_hosts is not defined and g_new_etcd_hosts is not defined}}
* use mux_client_mode instead of use_mux_clientRich Megginson2017-08-014-5/+15
| | | | | | | | | | | | | | | | | | | | | Instead of the `openshift_logging_use_mux_client` boolean parameter, use `openshift_logging_mux_client_mode` which will allow us to support different mux client use cases: The value `maximal` will cause Fluentd to perform as much of the processing as possible at the local node. This currently means all of the processing *except* for the Kubernetes metadata processing, which will be done by mux. This is the currently recommended mode to use due to current scaling issues. The value `minimal` means that Fluentd will do *no* processing at all, and send the raw logs to mux for processing. This is currently not recommended to use due to current scaling issues. Ansible will warn you if you try to use this mode. `MUX_ALLOW_EXTERNAL` is no longer needed in the mux dc. mux now always operates to process external logs. The ansible setting `openshift_logging_mux_allow_external` is still required in order to set up the mux service to accept connections from outside of the cluster.
* Impl fluentd file bufferNoriko Hosoi2017-07-282-0/+9
| | | | (cherry picked from commit 231a7c4ce27ff944d9e14169062f487f57c94dd6)
* Bug 1466152 - Json-file log driver: Neither ↵Rich Megginson2017-07-064-15/+7
| | | | | | | | | | "openshift_logging_fluentd_use_journal=false" nor omitted collects the log entries https://bugzilla.redhat.com/show_bug.cgi?id=1466152 Do not set openshift_logging_fluentd_use_journal or USE_JOURNAL at all unless it is explicitly set as an ansible param. It is almost always better to let fluentd figure out which log driver docker is using.
* add back mux_client config that was removedRich Megginson2017-07-052-0/+13
| | | | | | | not sure how this got removed, during the rebase of the logging roles perhaps? Also ensure that the value used in the fluentd daemonset env var is lower cased to work with the fluentd/run.sh script.
* Sync environment variables FLUENTD/MUX_CPU_LIMIT FLUENTD/MUX_MEMORY_LIMIT ↵Noriko Hosoi2017-06-271-2/+8
| | | | with the resource limit values.
* Fix typo in fluentd_secureforward_contents variableAndreas Dembach2017-06-271-1/+1
|
* Reverted most of this pr 4356 except:Noriko Hosoi2017-06-051-2/+2
| | | | | | | | | adding openshift_logging_fluentd_buffer_queue_limit: 1024 openshift_logging_fluentd_buffer_size_limit: 1m openshift_logging_mux_buffer_queue_limit: 1024 openshift_logging_mux_buffer_size_limit: 1m and setting the matched environment variables.
* Adding the defaults for openshift_logging_fluentd_{cpu,memory}_limit to ↵Noriko Hosoi2017-06-051-2/+2
| | | | | | | | roles/openshift_logging_fluentd/defaults/main.yml. Adding the description for openshift_hosted_logging_fluentd_{cpu,memory}_limit to README.md. Replaced openshift_hosted_logging_mux_.* with openshift_logging_mux_.*.
* Adding environment variables FLUENTD_CPU_LIMIT, FLUENTD_MEMORY_LIMIT, ↵Noriko Hosoi2017-06-021-0/+4
| | | | MUX_CPU_LIMIT, MUX_MEMORY_LIMIT.
* Introducing fluentd/mux buffer_queue_limit, buffer_size_limit, cpu_limit, ↵Noriko Hosoi2017-06-021-0/+4
| | | | | | | | | | | | | | | | and memory_limit. Default values: openshift_logging_fluentd_cpu_limit: 100m openshift_logging_fluentd_memory_limit: 512Mi openshift_logging_fluentd_buffer_queue_limit: 1024 openshift_logging_fluentd_buffer_size_limit: 16m openshift_logging_fluentd_buffer_size_limit: 1m openshift_logging_mux_cpu_limit: 500m openshift_logging_mux_memory_limit: 1Gi openshift_logging_mux_buffer_queue_limit: 1024 openshift_logging_mux_buffer_size_limit: 1m
* Pulling changes from master branchewolinetz2017-05-224-1/+20
|
* Pulling in changes from masterewolinetz2017-05-223-23/+39
|
* Decomposing openshift_logging role into subcomponent rolesewolinetz2017-05-2210-0/+509
generated by cgit v1.2.1 (git 2.18.0) at 2024-05-16 04:22:01 +0000