Getting Started with DAP

Provision the Deslicer Automation Platform for your tenant, create enrollment tokens, and enroll your first Splunk host in minutes.

Navigation

• Parent: Automation Platform
• Next: Insights Nodes
• Related: Deslicer Observer API

---

Step 1: Provision DAP

1. Navigate to Automation Platform → Platform in the dashboard sidebar.
2. The page opens on DAP Status. You see a Connection Status card showing "Not Configured."
3. Click Provision DAP.
4. The platform automatically connects your tenant to the Observer API. Once provisioned, the status changes to Connected with a green badge.

The DAP Status page displays the connection status, Observer API URL, integration state, feature profile, and provisioning timestamp. If the connection becomes degraded, you can self-repair it directly from this page. Shared settings and product-specific worker planes are described in Platform Planes.

Connection Status

The DAP connection card shows a badge indicating the current state:

Self-Repair

If DAP becomes disconnected or the AI integration is not wired, click Reconnect Integration on the Platform page. This re-provisions the connection without losing your enrolled nodes or change plan history. If DAP is not provisioned at all, the button reads Provision DAP instead.

Connectivity Warnings

When connectivity is degraded, a warning banner appears at the top of DAP sub-pages (Insights, Plans, Executions). The banner links to the DAP Platform page where you can view detailed diagnostics and trigger a repair.

Support Contact Card

When a connection issue persists, the Platform page displays a Support Contact Card with diagnostic details you can share with your administrator or Deslicer support: tenant ID, backend name, Observer API URL, HTTP status, error message, and a timestamp.

Step 2: Create an Enrollment Token

Enrollment tokens authenticate new hosts when they register with your tenant. You create separate tokens for Insights (Splunk add-on observability) and Worker Node (automation workers that execute change plans).

1. Navigate to Automation Platform → Platform → Splunk Enterprise → Enrollment.
2. Click New Token.
3. Choose a Purpose:
   • Insights (Splunk add-on) — enrolls the Insights modular input for configuration collection and fleet observability
   • Worker Node — enrolls a DAP worker for plan execution; does not require an Insights node on the same host
4. Enter a descriptive name (for example, production-forwarders or bootstrap-prod-sh1) and optional description.
5. Click Create Token.
6. A modal displays the token value with a 60-second countdown. Copy the token immediately — it is never stored in plain text and cannot be retrieved later.
7. The modal shows install instructions tailored to the token type:
   • Insights — Splunk add-on snippet with a link to Splunkbase and a configured app download when HTTPS is available
   • Worker — install snippets across Shell, Ansible, and Manual tabs. Copy the shell bootstrap command, Ansible playbook, or manual repository steps as needed.

Worker Install Tabs

For Worker tokens, the created-token dialog organizes install paths by method:

Each snippet has its own Copy button. An Install guide link opens step-by-step documentation for worker bootstrap enrollment.

Tenant Slug Requirement

Worker install snippets embed your tenant slug in download URLs and bootstrap commands. If the tenant slug is not configured, an amber banner explains that an enterprise administrator must set the slug before enrollment instructions can be generated. Contact your workspace administrator to complete tenant setup on the Enterprise → Tenants page.

Token Management

Each token shows its type, creation date, expiration, usage count, max hosts, enrolled hostnames, and status (Active or Revoked). Sort and search the token table to find tokens quickly.

Step 2b: Approve Pending Enrollments (When Required)

Tenant policy may require manual approval before a host receives credentials:

• Insights nodes — typically auto-approved
• Worker nodes — typically held for operator review on enterprise tenants

When approval is required, the host appears on Automation Platform → Pending Approvals after it registers. Review hostname, type, source IP, and Splunk version, then click Approve or Reject. See Pending Approvals for the full workflow.

After approval, assign the host on Inventory Groups before running compliance audits or change plans.

Step 3: Enroll a Node

Run the install command on any Splunk host:

curl -sSL https://install.deslicer.ai/node | ENROLLMENT_TOKEN=<your-token> bash

The Insights Node agent installs, authenticates with your enrollment token, and begins reporting to the platform. Within moments, the host appears on the Nodes page.

What Happens Next

Once enrolled, the Insights Node continuously reports:

• Operational state — hostname, IP address, Splunk version, agent version, last check-in
• Configuration snapshots — all Splunk .conf files and their stanzas
• App inventory — installed Splunk apps and their locations
• Certificate status — TLS certificates with expiration tracking

You can now browse your fleet from the Insights Nodes page and manage configurations via Change Plans.

Step 4: Configure Splunk Execution Credentials (Before Your First Rollout)

Plan execution requires Splunk management credentials so DAP workers can reach each target host. Navigate to Automation Platform → Platform → Splunk Enterprise → Splunk Credentials and add at least one credential:

• Tenant default — simplest starting point when hosts share one management account
• Host group or Specific host — when different tiers or hosts use different credentials

Deslicer checks credential coverage when you click Execute on an approved plan. If any targeted host is uncovered, rollout is blocked until you add the missing scope. See Splunk Execution Credentials for scope rules and the coverage hierarchy.