cancel
Showing results for 
Search instead for 
Did you mean: 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results for 
Search instead for 
Did you mean: 

Datadog Installation

Kayla
Valued Contributor II

Is anyone familiar with installing the Datadog agent on clusters? We're not having much luck. 
 We honestly might not be having the init script run since we're not seeing it in the log, but we can get just a generic "hellow world" init script to run and show in the log with no issue.

1 ACCEPTED SOLUTION

Accepted Solutions

Kayla
Valued Contributor II

Responding here with the solution I found. Hopefully it'll help anyone with similar issues.

First, the Datadog install script is practically a matryoshka doll- the script creates another script which creates a YAML file.
One of the consequences of that is that nothing from the original init script goes into the Databricks logs for init scripts. Instead, it writes its output to /tmp/datadog_start.log. The 2nd script that is created is also in the same directory at /tmp/start_datadog.sh, and I was able to use that to run it directly in a notebook and see the root cause of my error. The error itself was purely a syntax error, easily rectified when I was able to track it down.

View solution in original post

3 REPLIES 3

Walter_C
Databricks Employee
Databricks Employee

Is there any specific error you are receiving when running the init script? Does the run complete start up or fail due to the init script?

Kayla
Valued Contributor II

I'm not seeing any errors. The cluster does start up without issue.

Kayla
Valued Contributor II

Responding here with the solution I found. Hopefully it'll help anyone with similar issues.

First, the Datadog install script is practically a matryoshka doll- the script creates another script which creates a YAML file.
One of the consequences of that is that nothing from the original init script goes into the Databricks logs for init scripts. Instead, it writes its output to /tmp/datadog_start.log. The 2nd script that is created is also in the same directory at /tmp/start_datadog.sh, and I was able to use that to run it directly in a notebook and see the root cause of my error. The error itself was purely a syntax error, easily rectified when I was able to track it down.

Join Us as a Local Community Builder!

Passionate about hosting events and connecting people? Help us grow a vibrant local community—sign up today to get started!

Sign Up Now