wu-sheng opened a new issue, #10341:
URL: https://github.com/apache/skywalking/issues/10341

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no 
similar feature requirement.
   
   
   ### Description
   
   This is an open issue for new contributors. Apache Airflow is a widely used 
workflow scheduler. We are encouraging someone new to the community to add a 
new level catalog(**workflow**) for Airflow.
   
   ## Metrics
   Airflow exposes metrics through StatsD, 
https://airflow.apache.org/docs/apache-airflow/stable/administration-and-deployment/logging-monitoring/metrics.html.
 
   We could use StatsD + OpenTelemetry 
StatesD(https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/statsdreceiver/README.md)
 + OpenTelemetry OTEL exporter to ship the metrics to SkyWalking OTEL receiver.
   Then use MAL to build metrics as well as a dashboard for those metrics. 
Notice, a new layer and new UI menu should be added.
   
   ## Logging
   Airflow supports Fluents to ship metrics, 
https://airflow.apache.org/docs/apache-airflow/stable/administration-and-deployment/logging-monitoring/logging-architecture.html.
 SkyWalking already has FluentD setup support, so we should be able to receive 
and catalog the logs.
   
   Additionally, [Task 
Logs](https://airflow.apache.org/docs/apache-airflow/stable/administration-and-deployment/logging-monitoring/logging-tasks.html)
 seems an interesting think. We could use LAL(Log Analysis) to group the logs 
by task name(or ID) by treating tasks as endpoints(SkyWalking concept).
   
   
   ### Use case
   
   Add more observability for Airflow server. 
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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]

Reply via email to