--- title: "Application Performance Monitoring" slug: "application-performance-monitoring" updated: 2026-09-17T15:33:38Z published: 2026-09-17T15:33:38Z canonical: "docs.unqork.io/application-performance-monitoring" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.unqork.io/llms.txt > Use this file to discover all available pages before exploring further. # Application Performance Monitoring Unqork's APM (Application Performance Monitoring) integrates with [Datadog](https://www.datadoghq.com/) or [Splunk](https://www.splunk.com/) 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](/unqorkai/docs/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 | Limitation | Details | | --- | --- | | No metrics or logs | The telemetry feed does not include metrics or logs. Use trace data to build custom metrics and dashboards in the APM provider. | | No front-end telemetry | Telemetry covers server-side executions only. Client-side activity is not captured. | | No self-service setup | APM setup requires a support ticket. There is no in-platform configuration. | ## Requirements All three requirements must be met before submitting an enablement request. | # | Requirement | Details | | --- | --- | --- | | 1 | **Provider account** | An active, paid account with [Datadog](https://www.datadoghq.com/) or [Splunk](https://www.splunk.com/). | | 2 | **Plan** | Datadog requires a [Pro or Enterprise plan](https://www.datadoghq.com/pricing/). Free Datadog plans are not supported. Splunk requires the [Splunk Observability Cloud](https://www.splunk.com/en_us/products/observability-cloud.html) package. | | 3 | **Environment type** | The Unqork environment must be hosted on Kubernetes (K8s). | ## 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](https://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: | Tag | Description | | --- | --- | | `applicationId` | The application's unique identifier. | | `currentState` | The name of the workflow step. | | `otel.trace_id` | The trace's unique identifier. | | `userId` | The Creator who executed the workflow step. | ### 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](https://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: | Tag | Description | | --- | --- | | `component type` | The type of component executed (for example, Plug-In component). | | `Property ID` | The component's Property ID (for example, `plugCreateSubmissionError`). | | `module name` | The module where the component exists. | | `module ID` | The module's unique identifier. | --- **Changelog** | Date | Change | | --- | --- | | 2026-09-17 | Initial draft from v1 source (EN-8128). | In Unqork an application is a program used to perform specific tasks. An application can be one of two types: workflow or module. In software, telemetry is the automated process of collecting, transmitting, and analyzing data about an application's performance, usage, and health to gain insights and make improvements. This data can include metrics like crash reports, feature usage statistics, start-up times, and user behavior, which helps developers monitor systems, detect bugs, optimize performance, and enhance the user experience. End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product. Use the UAT (user acceptance testing) environment to realistically test and navigate your applications as end-users would use them. The Production environment is the final stage of the development process. Use this environment to promote tested and functioning application so your end-user can interact with it. APIs (application programming interfaces) are a set of protocols and definitions developers use to build and integrate application software. APIs act as the connective tissue between products and services. A key-value pair is a fundamental data structure where a unique "key" is associated with a specific "value," used for organizing and retrieving data efficiently, like in dictionaries or databases. Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform. A query lets you retrieve, access, manipulate, and delete data in a database. A Property ID is the unique field ID used by Unqork to track and link components in your module.