providers/redis/docs/logging/index.rst
.. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you 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.
.. _write-logs-redis:
Airflow can be configured to store log lines in Redis up to a configured maximum log lines, always keeping the most recent, up to a configured TTL. This deviates from other existing task handlers in that it accepts a connection ID. This allows it to be used in addition to other handlers, and so allows a graceful/reversible transition from one logging system to another. This is particularly useful in situations that use Redis as a message broker, where additional infrastructure isn't desired.
To enable this feature, airflow.cfg must be configured as in this example:
.. code-block:: ini
[logging]
remote_logging = True
remote_log_conn_id = redis_default
[redis]
# Optional configurations
# max_lines = 10000
# ttl_seconds = 2419200
Airflow uses the :ref:Redis Connection <howto/connection:redis> to connect to the Redis cluster.
If you have a connection with ID redis_default properly set up, Airflow will use it to read and write logs.
Logs are stored in Redis using keys generated with a template. The default template is
dag_id={dag_id}/run_id={run_id}/task_id={task_id}/attempt={try_number}.log.
Each key holds a Redis List containing the log lines.