AutomationDev85 commented on code in PR #67328:
URL: https://github.com/apache/airflow/pull/67328#discussion_r3380120773
##########
providers/edge3/docs/edge_executor.rst:
##########
@@ -217,3 +217,30 @@ Current Limitations Edge Executor
- Multi-team isolation is logical only — all teams share a single
authentication secret. A worker
administrator could change the team name and access another team's jobs.
See
:ref:`edge_executor:multi_team` for details and planned improvements.
+
+
+Metrics Export Compatibility
+-----------------------------
+
+The Edge Worker integrates with Airflow's statsd metrics system to export
runtime metrics. Compatibility
+between Edge provider versions and Airflow versions varies due to changes in
the metrics initialization
+pipeline. The table below documents known compatibility issues and workarounds:
+
+.. list-table::
+ :header-rows: 1
+
+ * - Provider version
+ - Airflow 3.3
+ - Airflow 3.2
+ - Airflow 3.1
+ * - >= 3.6.0
+ - Working
+ - Broken: webserver statsd initialization is missing
(DualStatsManager removed)
Review Comment:
I think with Airflow 3.2 and the provider version >= 3.6.0 edge metrics are
really broken as this is mentioned here:
https://github.com/apache/airflow/issues/68077.
##########
providers/edge3/docs/edge_executor.rst:
##########
@@ -217,3 +217,30 @@ Current Limitations Edge Executor
- Multi-team isolation is logical only — all teams share a single
authentication secret. A worker
administrator could change the team name and access another team's jobs.
See
:ref:`edge_executor:multi_team` for details and planned improvements.
+
+
+Metrics Export Compatibility
+-----------------------------
+
+The Edge Worker integrates with Airflow's statsd metrics system to export
runtime metrics. Compatibility
Review Comment:
good point will fix this.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
