> On 24 Oct 2025, at 18:38, Jarek Potiuk <[email protected]> wrote:
> I don't think what it could give us. Depending what "lite" means. I think
> the problem is that those who would not like to share the data are mostly
> concerned about "how many installations" they have (I am speaking mostly
> about our biggest stakeholders). It is perfectly understandable that they
> do not want to publish the "absolute numbers". And asking for that is
> like opening the business model books. Any "public matomo" reporting will
> necessarily expose that. There are mutliple ways the origin of reported
> data can be tracked to "where Airflow is installed" - and even if we do
> not, potentially malicious actors who break (potentially) to matomo
> instances of ASF could get such information. So from a business point of
> view that is a huge risk, and I expect no legal department would ever allow
> that. I think the only thing we can ask for is publish some aggregated
> data - but not automatically and not directly from running airflow.
If we strip out any local suffixes from the version so that we just see the
upstream OSS version (I.e. we have a version of 3.1.0+astro1, and as long as
the reporting code normalises this just to 3.1.0), then I will be making the
case internally that we leave this on for our SaaS offering. Given this
normalising, I cannot immediately see how you could tell if the Airflow install
is: someone running the OSS one on an EC2 box, using MWAA or running an
Astronomer deployment in AWS.
However I do have one thing that I think needs to change about the proposal.
The name: Telemetry is very closely tied with OpenTelemetry in my mind, and
even when Bolke first mentioned this to me before his talk I thought he was
talking about something else other than Analaytics/CallHome/PopularityContest.
I would propose calling this “Analytics”: “Would you like to report version and
usage analytics to help the Apache Airflow project?” etc.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
