Issue 1:
Apache Airflow version:

2.0.0b3

What happened:

When Airflow is ran within CeleryExecutor mode and using the new Cloudwatch integration (from #7437), log groups and log streams are created, but no log events are pushed to AWS. The Webserver is able to read the log stream as expected. There are no errors, just empty logs within Cloudwatch:

*** Reading remote log from Cloudwatch log_group: airflow-task log_stream: tutorial_taskflow_api_etl_dag/extract/2020-12-02T16_37_07.011589+00_00/1.log.

By switching to SequentialExecutor (default), with one container acting as both the scheduler and webserver, only then are the logs written as expected:

*** Reading remote log from Cloudwatch log_group: airflow-task log_stream: tutorial_taskflow_api_etl_dag/extract/2020-12-02T18_04_50.259906+00_00/1.log.
Task exited with return code 0
test
Exporting the following env vars:
AIRFLOW_CTX_DAG_OWNER=airflow
AIRFLOW_CTX_DAG_ID=tutorial_taskflow_api_etl_dag
AIRFLOW_CTX_TASK_ID=extract
AIRFLOW_CTX_EXECUTION_DATE=2020-12-02T18:04:50.259906+00:00
AIRFLOW_CTX_DAG_RUN_ID=manual__2020-12-02T18:04:50.259906+00:00
Running <TaskInstance: tutorial_taskflow_api_etl_dag.extract 2020-12-02T18:04:50.259906+00:00 [running]> on host 845928f08686
Started process 152 to run task
Executing <Task(_PythonDecoratedOperator): extract> on 2020-12-02T18:04:50.259906+00:00

--------------------------------------------------------------------------------
Starting attempt 1 of 1

--------------------------------------------------------------------------------
Dependencies all met for <TaskInstance: tutorial_taskflow_api_etl_dag.extract 2020-12-02T18:04:50.259906+00:00 [queued]>
Dependencies all met for <TaskInstance: tutorial_taskflow_api_etl_dag.extract 2020-12-02T18:04:50.259906+00:00 [queued]>

The logging configuration is turned on for the Scheduler, Webserver, and Workers. Log groups and log streams are being created as expected, but log events are not. There are no errors in the workers, and in AWS the IAM policy permissions are all-inclusive (they also definitely work with SequentialExecutor)

What you expected to happen:

I expected logs of tasks ran by the celery workers to display for the Webserver when ran with Cloudwatch Remote logging.

How to reproduce it:

Run Airflow 2.0.0b3 with Webserver in CeleryExecutor mode, two workers, 1 scheduler

Issue 2:
Apache Airflow Provider(s)

datadog

Versions of Apache Airflow Providers

apache-airflow-providers-datadog==3.0.0

Apache Airflow version

2.2.2

Operating System

Mac OS

Deployment

Amazon (AWS) MWAA

Deployment details

No response

What happened

I installed the provider package for DataDog. After installation I'm not getting any import errors when using the hook/operator in a DAG file, but I'm unable to create a DataDog connection through the Airflow UI.

I noticed in this file where other providers have a Connections section, Datadog does not.

https://github.com/apache/airflow/blob/main/airflow/providers/datadog/provider.yaml

What you think should happen instead

See above -- I believe some code is missing to actually allow the creation of a DataDog connection.

How to reproduce

Install the noted version of the Datadog provider package, through the airflow UI attempt to create a DataDog connection.

Anything else

No response

Are you willing to submit PR?

Yes I am willing to submit a PR!

Code of Conduct

I agree to follow this project's Code of Conduct