Application Performance Monitoring

Unqork's APM (Application Performance Monitoring) integrates with Datadog or Splunk to monitor application performance, availability, and health. APM uses OpenTelemetry (OTLP) to collect and forward server-side telemetry to the configured provider. Telemetry covers traces and spans from module, workflow, and component executions.

Note: APM covers server-side telemetry only and requires a support ticket to enable. To configure client-side session monitoring with Datadog, see Client Tracker Administration.

APM provides the following capabilities:

• Traces and Spans: Near-real-time trace and span telemetry for in-depth performance analysis.

• Server-Side Telemetry: All telemetry data covers server-side executions only, including module, workflow, and component executions. Front-end and client-side activity is not captured.

• Consistent Service Name: All Unqork telemetry appears under the service name unqork-applications in Datadog or Splunk.

APM enables teams to detect and resolve performance issues before they affect end-users or critical business processes.

Limitations

Requirements

All three requirements must be met before submitting an enablement request.

Enabling APM

Enabling APM requires coordination with Unqork's team. The typical SLA for connection setup is 3–5 business days after credentials are received.

To enable APM:

1. Submit a support ticket at support.unqork.com. Include the following details:

   #	Detail	Example
   1	Target environments	UAT, Production
   2	APM provider	Datadog or Splunk
   3	Provider instance link	datadoghq.com or datadoghq.eu

2. Share credentials securely: An Unqork team member is assigned to the ticket and provides a SendSafely link for secure credential submission:

   • Datadog: Datadog Secret (API) Key.

   • Splunk: API key with INGEST permissions.

3. Setup and configuration: The Unqork team configures the APM connection using the submitted credentials.

Datadog Integration

With Datadog APM, use telemetry to create metrics, alerts, and dashboards about application performance. Custom facets let teams filter by application context, including by module ID.

Viewing Traces

Traces are collections of correlated spans that provide a high-level view of what occurs when an application request is made. Access traces from APM in the Datadog side menu.

A Datadog trace for a workflow execution includes:

• The startNewSubmission parent operation.

• executeCurrentWorkflowStep child operations that run as part of the parent.

• The sequence in which child processes complete before the parent ends.

Viewing Spans

Spans provide detailed information about individual execution steps. Datadog tags on a span include:

Building Custom Metrics

Custom metrics let teams filter trace data by environment, application, or other attributes.

To create a custom metric in Datadog:

1. Go to app.datadoghq.com/apm/traces/generate-metrics.

2. Select New Metric.

3. In Set Metric Name, enter a name (for example, myApplication.duration).

4. In Define Query, enter one or more queries (for example, env:qa35-staging and @applicationId:64bfdf76ba2dfef968535d75).

5. Select Create Metric.

Use the metric to configure dynamic charts in a Datadog dashboard.

Splunk Integration

With Splunk APM, use visualization tools to display span attributes from Unqork executions.

Viewing Traces

Access spans from the Splunk left menu. A Splunk trace for a workflow execution includes:

• The unqork-applications:completeStep parent operation.

• unqork-applications:executeCurrentWorkflowStep child operations.

• Error traces, filterable by trace ID, execution step, duration, and error status.

Viewing Spans

Splunk span tags provide details about the executed component, including: