diff --git a/docs/_print/index.html b/docs/_print/index.html index 5cb895bf6..496ddc4f8 100644 --- a/docs/_print/index.html +++ b/docs/_print/index.html @@ -93,26 +93,12 @@
  • SyslogNGOutput - Defines a syslog-ng Output for a logging flow, where the log messages are sent using Fluentd. This is a namespaced resource. See also SyslogNGClusterOutput. To configure Fluentd outputs, see output.
  • SyslogNGFlow - Defines a syslog-ng logging flow using filters and outputs. Basically, the flow routes the selected log messages to the specified outputs. This is a namespaced resource. See also SyslogNGClusterFlow. To configure Fluentd flows, see flow.
  • SyslogNGClusterOutput - Defines a syslog-ng output that is available from all flows and clusterflows. The operator evaluates clusteroutputs in the controlNamespace only unless allowClusterResourcesFromAllNamespaces is set to true.
  • SyslogNGClusterFlow - Defines a syslog-ng logging flow that collects logs from all namespaces by default. The operator evaluates clusterflows in the controlNamespace only unless allowClusterResourcesFromAllNamespaces is set to true. To configure Fluentd clusterflows, see clusterflow.
  • For the detailed CRD documentation, see List of CRDs.

    Logging operator architecture

    Quickstart

    See our Quickstart guides.

    Support

    If you encounter problems while using the Logging operator the documentation does not address, open an issue or talk to us on Discord or Slack.

    1 - What's new

    Version 4.4

    The following are the highlights and main changes of Logging operator 4.4. For a complete list of changes and bugfixes, see the Logging operator 4.4 releases page.

    New syslog-ng features

    When using syslog-ng as the log aggregator, you can now use the following new outputs:

    You can now use the metrics-probe() parser of syslog-ng in syslogNGFLow and SyslogNGClusterFlow. For details, see MetricsProbe.

    Multitenancy with namespace-based routing

    Logging operator now supports namespace based routing for efficient aggregator-level multi-tenancy.

    In the project repository you can:

    On a side note, nodegroup level isolation for hard multitenancy is also supported, see the Nodegroup-based multitenancy example.

    Forwarder logs

    Fluent-bit now doesn’t process the logs of the Fluentd and syslog-ng forwarders by default to avoid infinitely growing message loops. With this change, you can access Fluentd and syslog-ng logs simply by running kubectl logs <name-of-forwarder-pod>

    In a future Logging operator version the logs of the aggregators will also be available for routing to external outputs.

    Timeout-based configuration checks

    You can now use timeout-based configuration strategies for both syslog-ng and Fluentd. For example:

    apiVersion: logging.banzaicloud.io/v1beta1
    -kind: Logging
    -metadata:
    -  name: all-to-file
    -spec:
    +
  • find an overview about multitenancy.
  • find more detailed information about the new LoggingRoute resource that enables this new behaviour.
  • find a simple example to demonstrate the new behaviour
  • On a side note, nodegroup level isolation for hard multitenancy is also supported, see the Nodegroup-based multitenancy example.

    Forwarder logs

    Fluent-bit now doesn’t process the logs of the Fluentd and syslog-ng forwarders by default to avoid infinitely growing message loops. With this change, you can access Fluentd and syslog-ng logs simply by running kubectl logs <name-of-forwarder-pod>

    In a future Logging operator version the logs of the aggregators will also be available for routing to external outputs.

    Timeout-based configuration checks

    Timeout-based configuration checks are different from the normal method: they start a Fluentd or syslog-ng instance +without the dry-run or syntax-check flags, so output plugins or destination drivers actually try to establish +connections and will fail if there are any issues , for example, with the credentials.

    Add the following to you Logging resource spec:

    spec:
       configCheck:
         strategy: StartWithTimeout
         timeoutSeconds: 5
    -  syslogNG: {}
    -  controlNamespace: default
    -
    apiVersion: logging.banzaicloud.io/v1beta1
    -kind: Logging
    -metadata:
    -  name: all-to-file
    -spec:
    -  configCheck:
    -    strategy: StartWithTimeout
    -    timeoutSeconds: 5
    -  fluentd: {}
    -  controlNamespace: default
     

    Istio support

    For jobs/individual pods that run to completion, Istio sidecar injection needs to be disabled, otherwise the affected pods would live forever with the running sidecar container. Configuration checkers and Fluentd drainer pods can be configured with the label sidecar.istio.io/inject set to false. You can configure Fluentd drainer labels in the Logging spec.

    Improved buffer metrics

    The buffer metrics are now available for both the Fluentd and the SyslogNG based aggregators.

    The sidecar configuration has been rewritten to add a new metric and improve performance by avoiding unnecessary cardinality.

    The name of the metric has been changed as well, but the original metric was kept in place to avoid breaking existing clients.

    Metrics currently supported by the sidecar

    Old

    +# HELP node_buffer_size_bytes Disk space used [deprecated]
     +# TYPE node_buffer_size_bytes gauge
     +node_buffer_size_bytes{entity="/buffers"} 32253
    diff --git a/docs/configuration/crds/extensions/eventtailer_types/index.html b/docs/configuration/crds/extensions/eventtailer_types/index.html
    index 1d60fa5bf..33f2b8690 100644
    --- a/docs/configuration/crds/extensions/eventtailer_types/index.html
    +++ b/docs/configuration/crds/extensions/eventtailer_types/index.html
    @@ -40,7 +40,7 @@
     Default: -">
     
     
    -
    +
     
     
    -
    +
     
     
     
    @@ -586,7 +586,7 @@
     

    EventTailer

    EventTailerSpec

    EventTailerSpec defines the desired state of EventTailer

    controlNamespace (string, required)

    The resources of EventTailer will be placed into this namespace

    Default: -

    positionVolume (volume.KubernetesVolume, optional)

    Volume definition for tracking fluentbit file positions (optional)

    Default: -

    workloadMetaOverrides (*types.MetaBase, optional)

    Override metadata of the created resources

    Default: -

    workloadOverrides (*types.PodSpecBase, optional)

    Override podSpec fields for the given statefulset

    Default: -

    containerOverrides (*types.ContainerBase, optional)

    Override container fields for the given statefulset

    Default: -

    EventTailerStatus

    EventTailerStatus defines the observed state of EventTailer

    EventTailer

    EventTailer is the Schema for the eventtailers API

    (metav1.TypeMeta, required)

    Default: -

    metadata (metav1.ObjectMeta, optional)

    Default: -

    spec (EventTailerSpec, optional)

    Default: -

    status (EventTailerStatus, optional)

    Default: -

    EventTailerList

    EventTailerList contains a list of EventTailer

    (metav1.TypeMeta, required)

    Default: -

    metadata (metav1.ListMeta, optional)

    Default: -

    items ([]EventTailer, required)

    Default: -