> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/~/revisions/1mY0CQn12Klyi0QiItHv/product-updates/whats-new.md).

# What's new?

## Nov 2025

#### Migrations (Public Preview)

We’re opening the public preview of fully automated migration from legacy observability stacks.\
From day one, the goal is simple: migrate *everything into groundcover, correctly, with one click.* Under the hood we:

* Figured out Data onboarding end to end - make sure your telemetry lands in the platform before anything else.
* Automatic conversion of monitors and dashboards
* Integrations discovery

[Check out the Migrations docs](https://docs.groundcover.com/getting-started/migrations)

<figure><img src="https://2771001740-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUHgqKYgCiRKdOpWQdi52%2Fuploads%2FQvl2eBw0EIeFb4VlGqci%2Fmigration_final.jpg?alt=media&amp;token=ccefc324-3ffb-436b-9c09-054d9c2d2718" alt=""><figcaption></figcaption></figure>

#### LLM Observability, now for AWS Bedrock

Our zero-instrumentation LLM Observability now supports AWS Bedrock calls.\
If you are building on Bedrock, you can get traces, latency breakdowns, token usage, and errors without changing your code.\
[Check out the LLM Observability docs](https://docs.groundcover.com/capabilities/llm-observability)<br>

<figure><img src="https://2771001740-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUHgqKYgCiRKdOpWQdi52%2Fuploads%2FDYZVrZo8uxnNrgDaY3zw%2Fbedrock.jpg?alt=media&amp;token=d8b21f81-5f1f-4ee9-b318-ae244938991a" alt=""><figcaption></figcaption></figure>

#### Data Sources: more integrations, better setup tools

We keep on expanding our list of supported integrations with the introduction of Azure metrics. In addition, we added support for Export to Terraform and Duplicate to ease the initial setup of integrations.\
[Check out the Data Sources docs](https://docs.groundcover.com/integrations/data-sources)<br>

<figure><img src="https://2771001740-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUHgqKYgCiRKdOpWQdi52%2Fuploads%2FhhyoVzrYcY7qlQbF22Iy%2FData%20Sources.jpg?alt=media&amp;token=d3b29273-c967-42ef-aee7-46338ed75a04" alt=""><figcaption></figcaption></figure>

#### Improvements across the app

We continued investing in core workstreams and shipped:

* Associated Variables in dashboards - highlights the most relevant values first.
* Formulas for Logs, Traces, Events, and RUM in Data Explorer/Dashboards.
* Dashboard Version History
* Custom chart colors for time series widgets


---

# 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.groundcover.com/~/revisions/1mY0CQn12Klyi0QiItHv/product-updates/whats-new.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.