Getting started with Davis CoPilot

Davis CoPilot is enabled on the account level by default, meaning that all your environments automatically have access to it. However, Davis CoPilot functionality must still be enabled on the environment level via the settings page, which offers you full control over how Davis CoPilot is enabled and configured in your environment.

Enable Davis CoPilot on your environment

If you can't see the settings page, make sure you have Setting Reader and Setting Writer policies assigned. For more information, see read and write permission.

User permissions

After enabling Davis CoPilot on the environment level, you'll still need to give access to Davis CoPilot to your users. To do so, you have to bind the group they belong to a policy with the following statement that allows access to Davis CoPilot:

For more information on managing your policies, see Manage IAM policies.

Davis CoPilot semantic index

Once enabled, Davis CoPilot periodically scans your Grail data to create its own semantic index. Certain data fragments are sent to Microsoft Azure OpenAI during the semantic indexing. Examples of such data fragments include metric keys, dimensions, and field names. When a user provides a prompt, Davis CoPilot first identifies the most relevant fragments from the data it has indexed. Davis CoPilot then sends the user prompt, the relevant data fragments, and some examples of field values observed in your environment to Microsoft Azure OpenAI for processing.

Enable environment-aware queries

Environment-aware queries can enrich Davis CoPilot with your environment's data. This lets you generate more accurate queries that identify and reference relevant entities, events, spans, logs, and metrics from your environment.

If you want Davis CoPilot to be aware of the details and structures of your environment's data, you'll need to allow access to Grail. To ensure you have full control over the security of your data, this functionality is opt-in, and admin users can specify which data tables and buckets Davis CoPilot is not allowed to access.

To enable environment-aware queries

It can take up to 24 hours for Davis CoPilot to build or amend the semantic index after changes are made. If environment-aware queries are disabled and the semantic index already exists, Davis CoPilot purges all environment-specific data within 24 hours, and returns to using publicly available sources for building DQL queries. The semantic index is stored only on your Dynatrace tenant.

Configure your data access

After enabling environment-aware queries, you'll be able to see the settings for configuring data that Davis CoPilot isn't allowed to access.

To configure your data access