# Continuous monitoring

All active positions are monitored continuously, in sync with new blockchain blocks. In practice, this means that every time the network produces a new block, the system updates the key metrics associated with each strategy.

These metrics include factors such as: 

* changes in available liquidity, 
* the health of collateralized positions, 
* deviations in stablecoin price stability, 
* governance proposals that could alter protocol parameters, 
* smart contract upgrades, 
* movements in oracle price feeds.

Monitoring is not performed for informational purposes alone. It feeds directly into Shift’s trigger system — a set of predefined rules that determine how the platform reacts when certain conditions are met.

A trigger can be thought of as an automated risk signal. When monitored metrics cross specific thresholds — for example, if liquidity drops sharply, a stablecoin begins to lose its peg, or a protocol governance proposal introduces new risk — the system flags the event and initiates the appropriate response.

Depending on the severity of the situation, a trigger may simply alert the risk team for review, or it may activate automated protective actions such as rebalancing positions or exiting a strategy entirely.

In this way, monitoring and triggers work together: monitoring detects changes in the environment, while triggers translate those changes into structured responses.

<br>


---

# Agent Instructions: 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:

```
GET https://docs.shiftdefi.com/user-docs/invest-with-confidence/safety-and-stress-scenarios/continuous-monitoring.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.