> For the complete documentation index, see [llms.txt](https://docs.linuxfoundation.org/lfx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.linuxfoundation.org/lfx/project-control-center/v2-latest-version/reports/health-metrics.md).

# Health Metrics

### Overview

Health metrics for open source projects are crucial for assessing their well-being, performance, and sustainability. These metrics assist stakeholders in gauging community engagement, activity levels, and the overall project environment.

The following are the main objectives of this feature:

* Provide visibility to the projects on areas to improve as per the OSS best practices guidelines for project setup.
* Monitor the project's health and take immediate action when the same starts deteriorating.
* Act as a checklist for the projects when they are ready to graduate.

### Step-by-Step Guide to Utilize Health Metrics

## Accessing Health Metrics

To access the Health Metrics report, perform the following steps:

1. Log in to your PCC account.
2. Search for the required project.
3. Click the 'Reports' tab.
4. Select **Health Metrics** to view the project's health report.

<figure><img src="/files/NsMr5DH13llALJy1NBkj" alt=""><figcaption><p>Health Metrics</p></figcaption></figure>


---

# 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 dynamically by asking a question.

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

```
GET https://docs.linuxfoundation.org/lfx/project-control-center/v2-latest-version/reports/health-metrics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.