/
Import Configuration for Datadog Importer

Import Configuration for Datadog Importer

Owned by Pio
Last updated: Mar 24, 2025 by Eva Ruzheva
3 min read

1. Build Objects/Attributes

After completing the Source and Destination configurations, it's time to create Object Types and their relationships based on the Datadog Data Model.

You can also choose to enable or disable Object Schema Sharing.

 

Pro Tip: Many of our customers create references from other Object Schemas and need access to the Datadog data. We recommend enabling Object Schema Sharing.

 

Review the options, then click the "Build Objects/Attributes" button.

image-20250324-121031.png

 

This step only needs to be completed once. Once the build is successful, you won’t need to repeat it. If this step has already been completed, a message will appear confirming it.

 

You may check your new Object Schema now and make sure the Object Types and Attributes are successfully created.

The Object Schema Graph will be as follows:

 

2. Test and Full Imports

You can test the configuration by clicking the Test Import button. This will import the first 100 Datadog hosts to your Object Schema. After the test runs, wait a few minutes for the process to complete, then check your Object Schema.

To monitor the progress, click the Check Import Status button to view the import execution status.

image-20250324-121416.png

If you are happy with the results of the test run, please run a manual full import. The minimum number of records you can import is 1000 by default. You can update this value from the Admin Tab.

3. Schedule

You have 4 options for the scheduling.

image-20250210-114122.png

  • Enable Hourly Imports: Runs the import once every hour when enabled.

  • Enable Daily Scheduled Imports: Runs the import once per day when enabled.

  • Enable Multiple Daily Scheduled Imports: Allows you to schedule imports at multiple time slots throughout the day.

  • Disable Scheduling: If you have a large number of records, the import may take time. We recommend testing it during off-peak hours when JSM usage is low.

 

Atlassian’s Forge platform operates on a unique scheduling mechanism that repeatedly invokes a function at specified intervals. Each trigger is designed to initiate shortly after its creation, typically around five minutes following app deployment. Subsequently, it executes according to the configured intervals—be it hourly, daily, or weekly. For more detailed information, please refer to Atlassian’s Documentation.

To customize the scheduling time, ensure that you install the app at the desired time.

 

 

Related content