OpenTelemetry Action

Actions for OpenTelemetry #

• Send Data. Send Lucidum data to OpenTelemetry.

Use Cases #

Below are the possible use cases for these actions:

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

• You can send specific sets of normalized, enriched Lucidum data to OpenTelemetry to be indexed, searched, and analyzed

Prerequisites #

To execute OpenTelemetry actions, you must:

• Configure a user account in OpenTelemetry with API permissions.

  NOTE. The specified account should have read and write permissions.

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

OpenTelemetry Configuration #

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

• URL. URL of the OpenTelemetry Collector.

• Max # of Records per Payload. Maximum number of Lucidum records to include in each execution of the action.

Create or Edit a New Action #

To create an action for OpenTelemetry:

1. In the Create a New Action page, in the General step, enter:

   

   • Description. After saving an Action, Lucidum uses the Luci LLM to populate this field automatically. You cannot edit the value in this field.
   • Business Value. After saving an Action, Lucidum uses the Luci LLM to populate this field automatically. You cannot edit the value in this field.
   • Action Type. Select an action from the pulldown options. Select Send 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.
   • Author Comments. Custom comments about the Action.

2. Click the Next (>) icon.

   

3. In the Filters page, click the Configure Filters button.

4. The Build a Query page appears.

   

5. In the Build a Query page, define the query to find the assets or users that the action will act upon.

6. For details on creating and editing queries in Lucidum, see the section on Creating 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.

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

8. Click the Next (>) icon.

9. In the Schedule page, enter the following:
   

   • 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.

10. Click the Next (>) icon.

11. 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, you can select these fields in the Query Results page > Edit Column button.

    • OpenTelemetry Service Name. Specify the new name of the OpenTelemetry service where you want to store Lucidum data.

    • Remove Space in the Field Name. If your implementation of OpenTelemetry does not accept field names that include spaces, toggle this field to “on”. Lucidum then automatically removes spaces in field names before sending the data.

    • 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 HappyFox.

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

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