Matthew R.

Del B., please don't tag @channel as it notifies everyone in this community subscribed to the channel, which is many more people (like me) than just the support folks themselves.

Srilakshmi C. our OPS team isn't available to support that during a meeting 😞, so I don't think it would be a very useful session without them, but I could be mistaken. I don't have a local dev instance of Airflow running. Maybe I should try to figure out how to do that via Docker or something... If you think it would still be useful to meet without being able to change and Airflow server side configs or package installations, then I'll definitely grab some time on your calendar.

got it, thanks!

Yes, thank you Mikyo and thanks again for asking this Helee!

Mikyo I'm using with self.tracer.start_as_current_span(...) as span: right now to create spans. Should the with using_metadata(metadata)...: clause be inside the highest level span that I want to associated the metadata with? or should the metadata clause be just above that span's with definition?

RunLLM is there any place where things like this are listed: "The Phoenix team is aware of this gap and has discussed adding more flexible column customization in the future, but it is not available as of now."? The user enhancement requests you linked are both closed. Neither of them addressed the issue satisfactorily.

Great question, Helee P.! RunLLM and Phoenix support folks, is this true: "The Phoenix UI will automatically surface these as columns"? I have quite a number of custom attributes in my spans set using the Python set_attribute method and they appear in my span's attributes dictionary in the Phoenix UI:

{
  "error": false,
  "airflow": {
    "dag_id": "<REDACTED>",
    "job_id": "102050913",
    "run_id": "scheduled__2025-09-25T10:55:00+00:00",
    "task_id": "<REDACTED>",
    "map_index": 0,
    "try_number": 1
  },
  "revenueio": {
    "vtt_key": "<REDACTED>",
    "call_key": "<REDACTED>",
    "job_type": "<REDACTED>",
    "account_id": 460,
    "agent_name": "User Search Service",
    "vtt_bucket": "<REDACTED>",
    "prompt_name": "<REDACTED>",
    "vtt_s3_path": "<REDACTED>",
    "host_user_id": 5346,
    "language_code": "en-US",
    "prompt_template": "<REDACTED>",
    "channel_mappings": "<REDACTED>",
    "recording_status_id": 63824,
    "min_words_to_process": 50,
    "min_seconds_to_process": 240
  },
  "openinference": {
    "span": {
      "kind": "CHAIN"
    }
  },
  "status_message": "Call processed successfully"
}

(Note, I used <REDACTED> to remove potentially sensitive values above...) But I don't see any of those automatically surfaced in as columns in the Phoenix UI:

Thanks for the offer Srilakshmi C.! Let me get back to you. 😊

Thanks!

RunLLM can you provide a Pipenv and requirement.txt file as well as the needed Airflow configurations files for the Airflow workers, scheduler, and web server (and any other parts of the base Airflow installation). I don't need these for the Airflow DAGs themselves. We are using Airflow 2.7.2 and a Celery based scheduler with multiple workers.