> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/kmp/setup-luciq-for-kmp/setup-application-performance-monitoring.md).

# Setup Application Performance Monitoring

Set up APM for your Kotlin Multiplatform app with Luciq. Monitor screen loading, network performance, app launch times, and custom traces.

APM tracks app launch, screen loading, screen rendering, flows (user journeys), and UI traces. You can enable/disable the whole feature or individual aspects.

* [App Launch](/kmp/setup-luciq-for-kmp/setup-application-performance-monitoring/app-launch.md) – Cold/warm app launch and `endAppLaunch()`
* [Screen Loading & Rendering](/kmp/setup-luciq-for-kmp/setup-application-performance-monitoring/screen-loading-and-rendering.md) – Screen loading and rendering tracking
* [Network](/kmp/setup-luciq-for-kmp/setup-application-performance-monitoring/network.md) – Network logging via Ktor plugin and `NetworkLogger`
* [Flows & UI Traces](/kmp/setup-luciq-for-kmp/setup-application-performance-monitoring/flows-and-ui-traces.md) – `startFlow`/`endFlow`, `startUITrace`/`endUITrace`
* [SDK Debugging](/kmp/setup-luciq-for-kmp/setup-application-performance-monitoring/sdk-debugging.md) – Debug logs (platform-specific)
* [Disabling/Enabling APM](/kmp/setup-luciq-for-kmp/setup-application-performance-monitoring/disabling-enabling-apm.md) – Turn APM on or off
* [Custom Spans](/kmp/setup-luciq-for-kmp/setup-application-performance-monitoring/custom-spans.md) – Custom spans (if supported by native SDK; see Flutter/React Native docs for concept)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.luciq.ai/kmp/setup-luciq-for-kmp/setup-application-performance-monitoring.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.