You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add fallbacks when retrieving databricks ids (#5910)
Add fallbacks when extracting databricks_job_id and databricks_task_run_id by adding searching in other properties if spark.databricks.job.id and spark.databricks.job.runId are not present
- spark.jobGroup.id that has the pattern <scheduler_id>_job-<job_id>-run-<task_run_id>-action-<action_id>
- spark.databricks.workload.id that has the pattern <org_id>-<job_id>-<task_run_id>
For databricks_job_run_id it will use:
- The new property spark.databricks.job.parentRunId as the default
- The current method of extracting the id present in the clusterName of job clusters as a fallback
The properties spark.databricks.job.id and spark.databricks.job.runId set by databricks are missing in some customer environnements
The property spark.databricks.job.parentRunId is a more robust way to extract the databricks_job_run_id
Copy file name to clipboardExpand all lines: dd-java-agent/instrumentation/spark/src/main/java/datadog/trace/instrumentation/spark/DatadogSparkListener.java
Copy file name to clipboardExpand all lines: dd-java-agent/instrumentation/spark/src/main/java/datadog/trace/instrumentation/spark/SparkConfAllowList.java
0 commit comments