summaryrefslogtreecommitdiffstats
path: root/roles/openshift_logging_fluentd/templates/fluentd.j2
Commit message (Collapse)AuthorAgeFilesLines
* Adding support for ES 5.x tech preview opt inEric Wolinetz2018-02-051-249/+0
|
* 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
* 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-191-4/+19
| | | | | | | | | | | | | | | 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-111-0/+22
| | | | 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).
* Added new variables for logging role for remote-syslog pluginstran2017-09-271-0/+46
| | | | | | | | 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
* | Remove logging ES_COPY featureJeff Cantrill2017-09-221-2/+0
|/
* 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
| |
* | Bug 1471322: logging roles based image versionsJan Wozniak2017-08-181-1/+1
|/ | | | | | Allowing to specify an image version for each logging component https://bugzilla.redhat.com/show_bug.cgi?id=1471322
* use mux_client_mode instead of use_mux_clientRich Megginson2017-08-011-4/+6
| | | | | | | | | | | | | | | | | | | | | 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-281-0/+7
| | | | (cherry picked from commit 231a7c4ce27ff944d9e14169062f487f57c94dd6)
* Bug 1466152 - Json-file log driver: Neither ↵Rich Megginson2017-07-061-2/+0
| | | | | | | | | | "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-051-0/+12
| | | | | | | 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.
* 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-221-0/+6
|
* Pulling in changes from masterewolinetz2017-05-221-7/+7
|
* Decomposing openshift_logging role into subcomponent rolesewolinetz2017-05-221-0/+117
generated by cgit v1.2.1 (git 2.18.0) at 2024-04-27 20:40:17 +0000