---
title: Collector failover
slug: concepts/collector-failover
docTags: GOo15ntkoXThxPf_Z8vVm
createdAt: 2025-09-05T08:27:39.019Z
---

It is possible to configure a collector to function as a failover collector for another collector.

## Normal operation

![](https://app.archbee.com/api/optimize/q2ez4Myy1Okvv4IuodiZe-G29tS3gnz_MtUQiqf7JDH-20250905-073743.png)

In normal operation the main collector is collecting data and “healthy”. The main collector will make its health available to the failover collector. As long as the failover collector can verify that the main collector is healthy it will remain idle.

An idle collector is still running but is not actively collecting data.

## Main collector is down

![](https://app.archbee.com/api/optimize/q2ez4Myy1Okvv4IuodiZe-dV3Jkhgg6jylsmquGplO5-20250905-073924.png)

In this scenario the failover collector has not been able to verify the health of the main collector in a predefined time frame, due to the main collector, or the machine it runs on, failing. In this case the failover collector will become active and start the collection of data on the failover server.

## Main collector is unhealthy but reachable

![](https://app.archbee.com/api/optimize/q2ez4Myy1Okvv4IuodiZe-aLkImbDxe-JPRseFeu2WN-20250905-074008.png)

In this scenario the failover collector received a health status from the main collector, but that status has been bad for a predefined time frame. In this case the failover collector will become active and start the collection of data on the failover server.

## Network down

![](https://app.archbee.com/api/optimize/q2ez4Myy1Okvv4IuodiZe-jxehZXlh0x3WbDa3-WFrJ-20250905-074044.png)

In this case the communication between the main collector and the failover collector is prevented by a network issue. In this case both collectors will collect data for the configured measurements.