# Apple Power & Performance Metrics

<div align="left"><img src="/files/ktnQEMKnxnGh3xBv4wNT" alt=""></div>

## Set up

### Navigate to the Integration settings view

1. Select an app in the top left corner from the Switcher
2. Navigate to **App Settings** by clicking the gear icon (⚙️) at the top of the Timeline sidebar
3. Click on **Integrations** in the sidebar

### **Connect Apple Power & Performance Metrics**

* Find the **Apple Power & Performance** integration module under the **Observability & analytics** section
* Click the **Connect** button
* Enter your ASC API key’s Key ID and Issuer ID, and upload the `.p8` key file
* Click **Save**; you’ll be presented with a dialog in which to select one or more metrics to monitor. Each metric offers 50th and 90th percentile measures, and available metric types include:
  * Disk writes
  * Hang rate
  * Battery usage (overall, on screen, background)
  * Launch time
  * Peak memory usage
  * Memory at suspension
  * Scroll hitch rate
  * Terminations (on screen, background)

{% hint style="info" %}
You can generate API keys within App Store Connect.

* You must be logged into App Store Connect with an **Admin** account to generate API keys.
* Runway requires an API key with the **App Manager** role.
* Runway currently supports **Team** private keys only.&#x20;

:link: [**Apple - Creating API Keys for App Store Connect API**](https://developer.apple.com/documentation/appstoreconnectapi/creating_api_keys_for_app_store_connect_api)
{% endhint %}

![Issuer ID, Key ID, and download link from the Users and Access section in App Store Connect](/files/whcGW3znUSt0k9WixGy6)


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.runway.team/integrations/observability-and-analytics/app-store-connect.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.