IBM Cloud Docs
Monitoring Spark application runs by using Databand

Monitoring Spark application runs by using Databand

Databand integration with Spark enhances monitoring capabilities by providing insights that extend beyond Spark UI and Spark History.

Databand improves Spark application monitoring by the following:

  • Advanced monitoring: Databand’s task annotations enable you to tag and track crucial stages of your Spark application, offering a more meaningful level of monitoring compared to Spark jobs, stages, or tasks.
  • Dataset tracking: Databand monitors the datasets that are accessed and modified during your Spark application run, providing enhanced visibility into your data flows.
  • Custom alerts: You can configure alerts for specific stages of your application or track key dataset metrics, allowing you to identify and address potential issues early.

To get started with Databand, you must have an active Databand subscription. You can obtain this by either requesting a Databand cloud application (SaaS) instance, which is deployed by the Databand team, or by opting for a self-hosted (on-premises) installation. For integrating databand with your watsonx.data instance, you must have the following credentials:

  • Environment address: The URL for your Databand environment (example: yourcompanyname.databand.ai).
  • Access token: A Databand access token that is needed to connect to the environment. You can generate and manage tokens through the Databand UI as required. For more details, visit: Managing personal access tokens.

Procedure

  1. Log in to the watsonx.data console.
  2. From the navigation menu, go to Configurations > IBM Data Observability by Databand.
  3. Enter the environment address in the URL field and the access token in the Access token field.
  4. Click Test connection to validate the connection.
  5. Click Save to save the details. You can edit the details by clicking Edit.

Databand takes effect for new Spark jobs that are started after enabling it. Previous and ongoing jobs are not recorded for analysis.

What to do next