-
Notifications
You must be signed in to change notification settings - Fork 15.5k
Description
Description
While using the Tableau Sensor to wait for a job to be completed, it only prints the job id into the log and not the friendly object type or name.
Please include the Object Name in the Sensor Log for any object (Workbook, Datasource, Fllow, User) rather than only the associated LUID. Currently it only lists the ID which gets hard to track and follow with dynamic tasks and other large volume installations.
Example of the current output of the Tableau Sensor Log: Note the highlighted items:
▶ Log message source details
[2025-04-23, 17:24:23 UTC] {local_task_job_runner.py:123} ▶ Pre task execution logs
[2025-04-23, 17:24:23 UTC] {base.py:84} INFO - Retrieving connection 'tableau_conn'
[2025-04-23, 17:24:23 UTC] {server.py:246} INFO - versions: 3.23, 2.4
[2025-04-23, 17:24:24 UTC] {auth_endpoint.py:91} INFO - Signed into https://tableau-corp.trinet.com/ as user with >id ae9999b4-de0a-9dfe-9b95-09d99ee999e7
[2025-04-23, 17:24:24 UTC] {jobs_endpoint.py:140} INFO - Query for information about job 99a9999e-b999-99a9->9fh9-bee99999f4c3
[2025-04-23, 17:24:24 UTC] {tableau.py:73} INFO - Current finishCode is SUCCESS (0)
[2025-04-23, 17:24:24 UTC] {auth_endpoint.py:115} INFO - Signed out
[2025-04-23, 17:24:24 UTC] {base.py:339} INFO - Success criteria met. Exiting.
[2025-04-23, 17:24:24 UTC] {taskinstance.py:341} ▶ Post task execution logs
NOTE: Can the following message include the type of object that fails to refresh? Currently it is hardcoded as a Workbook.
The output is hardcoded to "Workbook" regardless of if you are refreshing another object type such as a Datasource
- Code issue reference:
/providers.tableau.sensors.tableau.py
Use case/motivation
No response
Related issues
No response
Are you willing to submit a PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct