1fanwang commented on issue #66801: URL: https://github.com/apache/airflow/issues/66801#issuecomment-5276599409
> Why do you think it should be in Airflow as "standard" and not a separate project that you would place in https://airflow.apache.org/ecosystem/ - how do you know what we come up is "common" for people for use and not something specific for your particular use / deployment ? > > I am not strongly against it - but I woudl like to see some more rationale (and discussion on devlist explaining what exactly you are proposing and why you think this is generally usable by wide range of users of airflow and not a specific subset of thsoe. > > I would say this looks like we are trying to teach our users how to do dashboards / monitoring - but I think the approach of Airflow PMC is that airflow is a great scheduler for all kind of workflows, but we are not going to maintain everything for our users, unless this is something that is reusable by everone, tied to "scheduling" and not available as "generic" solution. > > The idea we had so far is airflow emits all kinds of raw metrics and it's up to the users how they are using them and we do not want to take responsibility for telling our users how to do it- we are neither experts nor we know what is the best approach and we are aware different kinds of slicing and dicing this information is probably depending on the kind of deployment you have. > > But maybe I do not understand that - this looks however as something that should be discussed on devlist as this seems to add "another thing that we commit to maintain" as a community Thanks for the push back @potiuk, checked this a bit more, OTel python sdk already has it: `OTEL_CONFIG_FILE` with `meter_provider.views[].selector.instrument_name` + `stream.aggregation`, supported in Python. Nothing for Airflow to own here. Closing. -- 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]
