You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by "kezhenxu94 (via GitHub)" <gi...@apache.org> on 2023/02/12 09:25:10 UTC

[GitHub] [skywalking] kezhenxu94 commented on issue #10341: [Feature] Setup dashboard for Airflow monitoring

kezhenxu94 commented on issue #10341:
URL: https://github.com/apache/skywalking/issues/10341#issuecomment-1426983742

   > > What tag do you need? Tag is not required. For describing airflow server, that could be set through otel collector, like we did for mysql metrics.
   > 
   > I mean that all info is contained in the "metrics name" such as <job_name>, <job_id>, <dag_id>, <task_id>, <operator_name>, and so on. But I have no way to filter and process. Or I just don't consider these metrics? Because of the statsD data format, the otel data collected will not have "key value pair" tag attributes.
   
   I doubt that you mixed the concept between "airflow job" and "opentelemetry job"? We use the OpenTelemetry Job name to distinguish data sources.
   
   As for the metrics name like `"local_task_job.task_exit.<job_id>.<dag_id>.<task_id>.<return_code>"`, I think you should spit them in the OpenTelemetry processor and move the metadata into tags then send to OAP, anyway I'll take a look at Airflow's doc to see what's the case.


-- 
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: notifications-unsubscribe@skywalking.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org