potiuk opened a new pull request, #36483:
URL: https://github.com/apache/airflow/pull/36483
Often our users are not aware that they are responsible for setting up and
monitoring the database they chose as the metaa-data backend.
While details of the tables and database structure of the metadata DB used
by Airflow is internal detail, the monitoring, tracking the usage, fine-tuning
and optimisation of the database configuration and detecting some cases where
database becomes a bottle neck is generally a task that Deployment Manager
should be aware of and it should be approached in a generic way - specific to
the database chosen by the Deployment Manager and it also depends a lot on the
choice of managed database if managed database is chosen by the Deployment
Manager.
This chapter makes it explicit and gives enough leads to the Deployment
Manager to be able to follow after they chose the database, it also explain the
specific parameters tha the Deployment Manager should pay attention to when
setting up such monitoring.
We also add an explanation of how Deployment Manager can setup client-side
logging of SQL queries generated by Airflow in case database access is
suspected for performance issues with Airflow, as a poor-man's version of
complete, server-side monitoring and explains caveats of such client side
configuraiton.
<!--
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.
-->
<!--
Thank you for contributing! Please make sure that your code changes
are covered with tests. And in case of new features or big changes
remember to adjust the documentation.
Feel free to ping committers for the review!
In case of an existing issue, reference it using one of the following:
closes: #ISSUE
related: #ISSUE
How to write a good git commit message:
http://chris.beams.io/posts/git-commit/
-->
<!-- Please keep an empty line above the dashes. -->
---
**^ Add meaningful description above**
Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
for more information.
In case of fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
In case of a new dependency, check compliance with the [ASF 3rd Party
License Policy](https://www.apache.org/legal/resolved.html#category-x).
In case of backwards incompatible changes please leave a note in a
newsfragment file, named `{pr_number}.significant.rst` or
`{issue_number}.significant.rst`, in
[newsfragments](https://github.com/apache/airflow/tree/main/newsfragments).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@airflow.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
