arjundevarajan commented on code in PR #39510:
URL: https://github.com/apache/airflow/pull/39510#discussion_r1595652416
##########
airflow/config_templates/config.yml:
##########
@@ -2591,3 +2591,22 @@ sensors:
type: float
example: ~
default: "604800"
+scarf_analytics:
+ description: |
+ Airflow integrates `Scarf <https://about.scarf.sh/>`__ to collect basic
telemetry data during operation.
+ This data assists Airflow maintainers in better understanding how Airflow
is used.
+ Insights gained from this telemetry are critical for prioritizing patches,
minor releases, and
+ security fixes. Additionally, this information supports key decisions
related to the development Roadmap.
+
+ Users can easily opt out of analytics in various ways documented
+ `here <https://docs.scarf.sh/gateway/#do-not-track>`__ and by setting the
``enabled`` option
Review Comment:
Hey @jedcunningham! I work on the Scarf team.
Hmm, maybe I can help provide some clarity here, but I'm not exactly sure
what the question is regarding the tracking pixels.
Scarf does provide a tracking pixel, and they are separate from the Gateway
(which, as you mentioned, does act as a proxy/redirect for things like
container images, files, Python packages, etc.), but the data from the two
mechanisms does get correlated in the Scarf platform.
Does that help answer what you're asking? Let me know if I'm
misinterpreting. Will definitely look to update our docs for further clarity
based on this discussion :)
--
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]
