Skip to content
This repository was archived by the owner on May 29, 2025. It is now read-only.

Conversation

@OjusWiZard
Copy link
Member

No description provided.

Signed-off-by: OjusWiZard <ojuswimail@gmail.com>
| Field | Type | Criteria |
| --- | --- | --- |
| `seconds_since_last_transition` | float | The number of seconds passed since the last transition in the FSM. |
| `is_tm_healthy` | bool | `false` if more than `BLOCKS_STALL_TOLERANCE` (60) seconds have passed since the last begin block request received from the tendermint node. `true` otherwise. |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This practically means that the agent <-> tm communication is all good.

| `rounds` | list | The last rounds (upto 25) in the FSM that happened including the current one. |
| `is_transitioning_fast` | bool | `true` if `is_tm_healthy` is `true` and `seconds_since_last_transition` is less than twice the `reset_pause_duration`. `false` otherwise. |

So, you can usually use `is_transitioning_fast` as a rule to check if an agent is healthly. To add a more strict check, you can also tune a threshold for the `seconds_since_last_transition` and rate of change of `period`, but that will require some monitoring to fine tune it.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's also quite easy to add more metrics, although changes to the agent code would be required.

@0xArdi 0xArdi merged commit 869cf13 into valory-xyz:develop Oct 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants