jedcunningham commented on code in PR #69633: URL: https://github.com/apache/airflow/pull/69633#discussion_r3561107476
########## airflow-core/newsfragments/69633.feature.rst: ########## Review Comment: Delete this. ########## airflow-core/docs/administration-and-deployment/logging-monitoring/traces.rst: ########## @@ -87,6 +87,35 @@ Custom spans created this way are automatically nested as children of the Airflo task span when tracing is enabled. When tracing is disabled, the no-op tracer provided by the OpenTelemetry API is used, so tasks run without any overhead. +Per-run trace controls (run conf) +--------------------------------- + +A few reserved keys in a Dag run's ``conf`` let you control tracing for that individual run. +They are read when the run is created (and when it is cleared), so set them when you trigger the +run — from the UI/API "Trigger with config" dialog, the ``airflow dags trigger --conf`` CLI, or +``TriggerDagRunOperator(conf=...)``. + +``airflow/trace_sampled`` + Force the head-sampling decision for this run. ``true`` always traces the run and ``false`` + never does, regardless of the configured sampler; omit the key to let the sampler decide. + Only an explicit boolean is honored. + +``airflow/task_span_detail_level`` + Integer detail level controlling how many spans task execution emits for this run. Review Comment: It might be nice to explain the range that is meaningful. -- 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]
