Add filtering support to Audit Log view

[vatsrahul1001]

closes: #53055#53050

Testing
UI:

Filter by User

Filter by DAG_ID

Filter by Task ID

Filter by RUN_ID

Filter by Event Type

Filter by Dates

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
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 airflow-core/newsfragments.

[pierrejeambrun]

Thanks.

Functional but there are a few things to improve before we can merge.

[pierrejeambrun]

We also need lables on the datetime fields, like this:

Or it's impossible to know what the input is for.

[pierrejeambrun]

Also for dag_id you are filtering on dag_id, but what we actually show in the UI is the dag_display_name. We need to filter on dag_display_name so there is no inconsistency between what is displayed to the user in the table and what the filter is operating on. Similarly to #54049, it should also probably be a search, i.e use the seach bar and use a pattern on the dag_display_name.

[pierrejeambrun]

Nice. A few more comments.

[bbovenzi]

For a follow up PR, I wonder if we would want to move the search boxes into the table header to save space and keep a better association of what you're searching:

https://tanstack.com/table/latest/docs/framework/react/examples/filters-fuzzy

[bbovenzi]

For a follow up PR, I wonder if we would want to move the search boxes into the table header to save space and keep a better association of what you're searching:

https://tanstack.com/table/latest/docs/framework/react/examples/filters-fuzzy

Actually, scratch this idea. We'll probably move them into an "Advanced Search" dropdown like originally planned

[bbovenzi]

Looking good. Just a few more comments to clean up the code

[bbovenzi]

Great work!

[vatsrahul1001]

closes: #53055#53050

Testing
UI:

Filter by User

Filter by DAG_ID

Filter by Task ID

Filter by RUN_ID

Filter by Event Type

Filter by Dates

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
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 airflow-core/newsfragments.

[pierrejeambrun]

Thanks.

Functional but there are a few things to improve before we can merge.

[pierrejeambrun]

We also need lables on the datetime fields, like this:

Or it's impossible to know what the input is for.

[pierrejeambrun]

Also for dag_id you are filtering on dag_id, but what we actually show in the UI is the dag_display_name. We need to filter on dag_display_name so there is no inconsistency between what is displayed to the user in the table and what the filter is operating on. Similarly to #54049, it should also probably be a search, i.e use the seach bar and use a pattern on the dag_display_name.

[pierrejeambrun]

Nice. A few more comments.

[bbovenzi]

For a follow up PR, I wonder if we would want to move the search boxes into the table header to save space and keep a better association of what you're searching:

https://tanstack.com/table/latest/docs/framework/react/examples/filters-fuzzy

[bbovenzi]

For a follow up PR, I wonder if we would want to move the search boxes into the table header to save space and keep a better association of what you're searching:

https://tanstack.com/table/latest/docs/framework/react/examples/filters-fuzzy

Actually, scratch this idea. We'll probably move them into an "Advanced Search" dropdown like originally planned

[bbovenzi]

Looking good. Just a few more comments to clean up the code

[bbovenzi]

Great work!

[vatsrahul1001]

closes: #53055#53050

Testing
UI:

Filter by User

Filter by DAG_ID

Filter by Task ID

Filter by RUN_ID

Filter by Event Type

Filter by Dates

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
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 airflow-core/newsfragments.

[pierrejeambrun]

Thanks.

Functional but there are a few things to improve before we can merge.

[pierrejeambrun]

We also need lables on the datetime fields, like this:

Or it's impossible to know what the input is for.

[pierrejeambrun]

Also for dag_id you are filtering on dag_id, but what we actually show in the UI is the dag_display_name. We need to filter on dag_display_name so there is no inconsistency between what is displayed to the user in the table and what the filter is operating on. Similarly to #54049, it should also probably be a search, i.e use the seach bar and use a pattern on the dag_display_name.

[pierrejeambrun]

Nice. A few more comments.

[bbovenzi]

For a follow up PR, I wonder if we would want to move the search boxes into the table header to save space and keep a better association of what you're searching:

https://tanstack.com/table/latest/docs/framework/react/examples/filters-fuzzy

[bbovenzi]

For a follow up PR, I wonder if we would want to move the search boxes into the table header to save space and keep a better association of what you're searching:

https://tanstack.com/table/latest/docs/framework/react/examples/filters-fuzzy

Actually, scratch this idea. We'll probably move them into an "Advanced Search" dropdown like originally planned

[bbovenzi]

Looking good. Just a few more comments to clean up the code

[bbovenzi]

Great work!

[vatsrahul1001]

closes: #53055#53050

Testing
UI:

Filter by User

Filter by DAG_ID

Filter by Task ID

Filter by RUN_ID

Filter by Event Type

Filter by Dates

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
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 airflow-core/newsfragments.

[pierrejeambrun]

Thanks.

Functional but there are a few things to improve before we can merge.

[pierrejeambrun]

We also need lables on the datetime fields, like this:

Or it's impossible to know what the input is for.

[pierrejeambrun]

Also for dag_id you are filtering on dag_id, but what we actually show in the UI is the dag_display_name. We need to filter on dag_display_name so there is no inconsistency between what is displayed to the user in the table and what the filter is operating on. Similarly to #54049, it should also probably be a search, i.e use the seach bar and use a pattern on the dag_display_name.

[pierrejeambrun]

Nice. A few more comments.

[bbovenzi]

For a follow up PR, I wonder if we would want to move the search boxes into the table header to save space and keep a better association of what you're searching:

https://tanstack.com/table/latest/docs/framework/react/examples/filters-fuzzy

[bbovenzi]

For a follow up PR, I wonder if we would want to move the search boxes into the table header to save space and keep a better association of what you're searching:

https://tanstack.com/table/latest/docs/framework/react/examples/filters-fuzzy

Actually, scratch this idea. We'll probably move them into an "Advanced Search" dropdown like originally planned

[bbovenzi]

Looking good. Just a few more comments to clean up the code

[bbovenzi]

Great work!

[vatsrahul1001]

closes: #53055#53050

Testing
UI:

Filter by User

Filter by DAG_ID

Filter by Task ID

Filter by RUN_ID

Filter by Event Type

Filter by Dates

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
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 airflow-core/newsfragments.

[pierrejeambrun]

Thanks.

Functional but there are a few things to improve before we can merge.

[pierrejeambrun]

We also need lables on the datetime fields, like this:

Or it's impossible to know what the input is for.

[pierrejeambrun]

Also for dag_id you are filtering on dag_id, but what we actually show in the UI is the dag_display_name. We need to filter on dag_display_name so there is no inconsistency between what is displayed to the user in the table and what the filter is operating on. Similarly to #54049, it should also probably be a search, i.e use the seach bar and use a pattern on the dag_display_name.

[pierrejeambrun]

Nice. A few more comments.

[bbovenzi]

For a follow up PR, I wonder if we would want to move the search boxes into the table header to save space and keep a better association of what you're searching:

https://tanstack.com/table/latest/docs/framework/react/examples/filters-fuzzy

[bbovenzi]

For a follow up PR, I wonder if we would want to move the search boxes into the table header to save space and keep a better association of what you're searching:

https://tanstack.com/table/latest/docs/framework/react/examples/filters-fuzzy

Actually, scratch this idea. We'll probably move them into an "Advanced Search" dropdown like originally planned

[bbovenzi]

Looking good. Just a few more comments to clean up the code

[bbovenzi]

Great work!

[vatsrahul1001]

closes: #53055#53050

Testing
UI:

Filter by User

Filter by DAG_ID

Filter by Task ID

Filter by RUN_ID

Filter by Event Type

Filter by Dates

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
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 airflow-core/newsfragments.

[pierrejeambrun]

Thanks.

Functional but there are a few things to improve before we can merge.

[pierrejeambrun]

We also need lables on the datetime fields, like this:

Or it's impossible to know what the input is for.

[pierrejeambrun]

Also for dag_id you are filtering on dag_id, but what we actually show in the UI is the dag_display_name. We need to filter on dag_display_name so there is no inconsistency between what is displayed to the user in the table and what the filter is operating on. Similarly to #54049, it should also probably be a search, i.e use the seach bar and use a pattern on the dag_display_name.

[pierrejeambrun]

Nice. A few more comments.

[bbovenzi]

For a follow up PR, I wonder if we would want to move the search boxes into the table header to save space and keep a better association of what you're searching:

https://tanstack.com/table/latest/docs/framework/react/examples/filters-fuzzy

[bbovenzi]

For a follow up PR, I wonder if we would want to move the search boxes into the table header to save space and keep a better association of what you're searching:

https://tanstack.com/table/latest/docs/framework/react/examples/filters-fuzzy

Actually, scratch this idea. We'll probably move them into an "Advanced Search" dropdown like originally planned

[bbovenzi]

Looking good. Just a few more comments to clean up the code

[bbovenzi]

Great work!

[vatsrahul1001]

closes: #53055#53050

Testing
UI:

Filter by User

Filter by DAG_ID

Filter by Task ID

Filter by RUN_ID

Filter by Event Type

Filter by Dates

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
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 airflow-core/newsfragments.

[pierrejeambrun]

Thanks.

Functional but there are a few things to improve before we can merge.

[pierrejeambrun]

We also need lables on the datetime fields, like this:

Or it's impossible to know what the input is for.

[pierrejeambrun]

Also for dag_id you are filtering on dag_id, but what we actually show in the UI is the dag_display_name. We need to filter on dag_display_name so there is no inconsistency between what is displayed to the user in the table and what the filter is operating on. Similarly to #54049, it should also probably be a search, i.e use the seach bar and use a pattern on the dag_display_name.

[pierrejeambrun]

Nice. A few more comments.

[bbovenzi]

For a follow up PR, I wonder if we would want to move the search boxes into the table header to save space and keep a better association of what you're searching:

https://tanstack.com/table/latest/docs/framework/react/examples/filters-fuzzy

[bbovenzi]

For a follow up PR, I wonder if we would want to move the search boxes into the table header to save space and keep a better association of what you're searching:

https://tanstack.com/table/latest/docs/framework/react/examples/filters-fuzzy

Actually, scratch this idea. We'll probably move them into an "Advanced Search" dropdown like originally planned

[bbovenzi]

Looking good. Just a few more comments to clean up the code

[bbovenzi]

Great work!

[vatsrahul1001]

closes: #53055#53050

Testing
UI:

Filter by User

Filter by DAG_ID

Filter by Task ID

Filter by RUN_ID

Filter by Event Type

Filter by Dates

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
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 airflow-core/newsfragments.

[pierrejeambrun]

Thanks.

Functional but there are a few things to improve before we can merge.

[pierrejeambrun]

We also need lables on the datetime fields, like this:

Or it's impossible to know what the input is for.

[pierrejeambrun]

Also for dag_id you are filtering on dag_id, but what we actually show in the UI is the dag_display_name. We need to filter on dag_display_name so there is no inconsistency between what is displayed to the user in the table and what the filter is operating on. Similarly to #54049, it should also probably be a search, i.e use the seach bar and use a pattern on the dag_display_name.

[pierrejeambrun]

Nice. A few more comments.

[bbovenzi]

For a follow up PR, I wonder if we would want to move the search boxes into the table header to save space and keep a better association of what you're searching:

https://tanstack.com/table/latest/docs/framework/react/examples/filters-fuzzy

[bbovenzi]

For a follow up PR, I wonder if we would want to move the search boxes into the table header to save space and keep a better association of what you're searching:

https://tanstack.com/table/latest/docs/framework/react/examples/filters-fuzzy

Actually, scratch this idea. We'll probably move them into an "Advanced Search" dropdown like originally planned

[bbovenzi]

Looking good. Just a few more comments to clean up the code

[bbovenzi]

Great work!