Dynatrace Actions

Actions for Dynatrace #

• Send Data to Dynatrace. Sends a custom set of Lucidum data to Dynatrace logs.

• Send Device to Dynatrace. Create a new device in Dynatrace, populated with Lucidum data.

Use Cases #

Below are the possible use cases for these actions:

• If you want to run Lucidum “headless”, you can send relevant data to Dynatrace on a regular schedule.

• You can send normalized, enriched Lucidum data to Dynatrace to be indexed, searched, and analyzed.

Prerequisites #

To execute Dynatrace actions, you must

Configure a Dynatrace API connection beforehand. The required parameters are described in the instructions for creating a Dynatrace connector in Lucidum https://lucidum.io/docs/dynatrace/.

Workflows #

• Creating a new Configuration and a new Action
• Cloning an Existing Action
• Creating a new Action from the Location Results page
• Editing a Configuration
• Editing an Action
• Viewing Information about an Action

Dynatrace Configuration #

To create a configuration for Dynatrace actions:

• Configuration Name. Identifier for the Configuration. This name will appear in the Lucidum Action Center.

• Activegate Domain (Optional). If you are using Activegate, specify the URL for Activegate. The URL for your Dynatrace system includes the Activegate domain.

  • The URL is of the format https://<your-activegate-domain>/e/<your-environment-id>/

• Dynatrace Domain. For on-premises implementations. The URL for your Dynatrace system includes the Dynatrace domain.

  • The URL is of the format https://<your-domain>/e/<your-environment-id>/

• Deployment (required). Type of deployment, specified with an integer. Choices are:

  • 1. Managed deployment

  • 2 SAAS deployment

  • 3. Activegate deployment

• Environment ID (required). The environment ID for the environment you want to ingest with the Lucidum connector. Each environment in Dynatrace is identified with a unique ID..

  • To find your environment ID, log in to Dynatrace, click the User button in the upper-right corner of the menu bar, and select Account settings.

• Access Token (required). Specify the API token for a Dynatrace account with the scope “logs.ingest” for Send Data actions and “entities.write” for Send Device actions. For more details, see https://docs.dynatrace.com/docs/dynatrace-api/basics/dynatrace-api-authentication

• Max # of Records per Payload. The maximum number of records to send to Dynatrace in each action. The default value is “50”.

Create a New Action #

To create an action for Datadog:

1. Go to the Create a New Action page.

   

2. In the General step, enter values in these fields:

   • Action Type. Select Send Data or Create Incident.

     • Send Data. Send Lucidum data to Dynatrace logs.

     • Send Device. Create a new device in Dynatrace, populated with Lucidum data.

   • Configuration Name. Select an action configuration from the pulldown options.

   • Action Name. Identifier for the action. This name will appear in the Lucidum Action Center.

   • Description. Description of the action.

3. Click the Next (>) icon.

4. In the Filters page, click Configure Filters.

   /li>

5. The Build a Query page appears.

   

6. In the Build a Query page, you define the query for the assets or users that the action will act upon.

7. Click Next.

8. In the Build a Current Query page, enter the fields, operators, and values for the query. For existing actions, the query is already loaded in this page.

   

9. For details on creating and editing queries in Lucidum, see the section on Building Queries.

   NOTE: To optimize performance, the default time range is Current. If you need to access historical data, contact Lucidum Custom Success for help on using historical data without affecting performance.

10. Click the Apply (page and pencil) icon.

11. Click the Next (>) icon.

12. The Schedule page appears.

    

13. In the Schedule page, enter:

    • Schedule Type. Define the schedule for the action. Choices are:

      • Recurrence. Specify a frequency for the recurring schedule.

      • After Data Ingestion. The action is executed after data ingestion, which happens at least once every 24 hours and can also be triggered manually.

    • Do not trigger the action unless. Specify the number of results from Filters as a prerequisite for executing the action.

14. Click the Next (>) icon.

15. The Details step looks like this:

    

16. In the Details page, enter the following:

    • Output Fields. For the records selected with the Filters field, specify the columns to display. When creating or editing the query in the Filters field, you can select these fields in the Query Results page > Edit Column button.

    • Dedupe Previous Jobs. In this field, you specify whether you want duplicates of asset IDs (if your query is for assets) or user IDs (if your query is for users). You can specify integers starting at 0 (zero).

      • If you specify “0” (zero), Lucidum includes all the records from the query in each delivery to Dynatrace.

      • If you specify “1” (one), Lucidum examines the previous webhook payload and excludes records for asset IDs or user IDs that were sent in the delivery to Dynatrace.

      • If you specify “2” (two), Lucidum examines the last two webhook payloads and excludes records for asset IDs or user IDs that were sent in the previous two deliveries to Dynatrace.