Skip to content

fix(docs): improve real-time monitoring faq #1050

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dineshpinto merged 1 commit into from
Dec 1, 2025
Merged

fix(docs): improve real-time monitoring faq #1050

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 31 additions & 3 deletions docs/run-node/5-flare-entity.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -980,10 +980,38 @@ To opt-out of receiving all future FlareDrops, you need to call the [`optOutOfAi
</details>

<details>
<summary>F6. How do I get real-time Slack/Discord/Telegram alerts for my Flare Entity?</summary>
<summary>F6. How do I get real-time Slack/Discord/Telegram alerts for issues with my Flare Entity?</summary>

Try out the alpha version of the [flare-foundation/fsp-observer](https://github.com/flare-foundation/fsp-observer) to receive instant notifications about critical misbehaviors - like FTSO or FDC reveal offenses, registration failures, and more - that could cost rewards.
To receive instant notifications about critical validator or data provider issues - such as FTSO or FDC reveal offenses, registration failures, and more - use the [flare-foundation/fsp-observer](https://github.com/flare-foundation/fsp-observer) monitoring service.

We would appreciate feature requests to direct development of the tool, please raise them on the [issues page](https://github.com/flare-foundation/fsp-observer/issues).
1. Create a env file (e.g., `.env.fsp-observer`) with your configuration:

```plaintext title=".env.fsp-observer"
# Required
RPC_BASE_URL="https://flare-api.flare.network" # Flare RPC endpoint
IDENTITY_ADDRESS="0x0000000000000000000000000000000000000000" # your identity address

# Optional notification channels
NOTIFICATION_DISCORD_WEBHOOK="https://discord.com/api/webhooks/..."
NOTIFICATION_TELEGRAM_BOT_TOKEN="your-telegram-bot-token"
NOTIFICATION_TELEGRAM_CHAT_ID="your-telegram-chat-id"
NOTIFICATION_SLACK_WEBHOOK="https://hooks.slack.com/services/..."
NOTIFICATION_GENERIC_WEBHOOK="http://host:port/path" # generic POST webhook
```

:::warning

Make sure this env file is **not committed** to version control (add it to `.gitignore` if needed).

:::

2. Run the observer using Docker:

```bash
docker run --env-file .env.fsp-observer ghcr.io/flare-foundation/fsp-observer:main
```

The container will watch your identity and send notifications to any configured channels when issues are detected.
If you encounter problems or have feature requests, open an issue on the [GitHub issues page](https://github.com/flare-foundation/fsp-observer/issues).

</details>