> ## Documentation Index
> Fetch the complete documentation index at: https://docs.heygarth.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Heartbeat to Garth

## Overview

G360 includes an optional health monitoring feature called the **Heartbeat**.

When enabled, G360 periodically sends a signed health update to the Garth platform.

This helps provide visibility into the general health and status of the G360 environment.

The Heartbeat feature is disabled by default.

## What Information Is Sent

The Heartbeat can provide general information about the G360 environment, including:

* G360 version and build information
* Container image versions
* PostgreSQL health
* Redis health
* Celery health
* General system and estate counts

This information can help support teams understand the general state of a G360 deployment.

## What Information Is Not Sent

The Heartbeat does not send sensitive operational information such as:

* User names
* Project names
* Connection names
* Repository names
* Individual metric values

## Network Requirements

When enabled, the Heartbeat communicates with the Garth platform using outbound HTTPS.

The connection uses:

```text theme={null}
https://app.heygarth.ai
```

Outbound access over port `443` is required.

## How the Heartbeat Works

G360 periodically sends:

* Health information
* A daily inventory snapshot

If G360 cannot connect to the Garth platform, the information is queued locally and retried later.

<Note>
  Heartbeat connectivity issues do not affect the normal operation of G360.
</Note>

## Enabling the Heartbeat

The Heartbeat feature is disabled by default.

It can be enabled using the following environment configuration:

```text theme={null}
G360_TELEMETRY_ENABLED=true
```

This configuration is typically managed during installation or deployment.

## If the Heartbeat Is Disabled

G360 continues to operate normally when the Heartbeat feature is disabled.

However, remote support teams have less visibility into:

* The version of G360 running in your environment
* The health of major G360 components
* General deployment status

Your organization can decide whether to enable the feature based on its internal security and data-sharing policies.

## Next Steps

Once your G360 environment has been prepared and deployed, you can begin connecting your organization's tools.

Continue to the **Tool Integrations** section to configure supported integrations.