sendnrw/netbird-docs
2
0
Fork 0
mirror of https://github.com/netbirdio/docs.git synced 2026-10-10 23:59:04 +02:00
Code Issues Packages Projects Releases Wiki Activity

Added mention of peer disconnection notification feature to networks docs (#706)

Browse Source
This commit is contained in:
shuuri-labs
2026-04-20 17:13:43 +02:00
committed by GitHub
parent dea78e302f
commit 79c99b23ab
3 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/pages/manage/networks/index.mdx
+4
View File
@@ -34,6 +34,10 @@ You can add multiple routing peers using individual peers or groups to ensure hi
<img src="/docs-static/img/manage/networks/index/add-routing-peer-1.png" alt="high-level-dia" className="imagewrapper"/> <img src="/docs-static/img/manage/networks/index/add-routing-peer-1.png" alt="high-level-dia" className="imagewrapper"/>
</p> </p>
<Note>
To get alerted when a routing peer goes offline, enable the **Routing Peer Disconnected** event in [Notifications](/manage/settings/notifications). You can receive alerts via email, webhook, or Slack.
</Note>
<Note> <Note>
A network resource policy grants access to the network **behind** the routing peer, not to the routing peer machine itself. If you need to access services running on the routing peer (for example, Pi-hole, Home Assistant, or a monitoring dashboard), add the routing peer to a group and create a peer-to-peer [access control policy](/manage/access-control) with that group as the destination. A network resource policy grants access to the network **behind** the routing peer, not to the routing peer machine itself. If you need to access services running on the routing peer (for example, Pi-hole, Home Assistant, or a monitoring dashboard), add the routing peer to a group and create a peer-to-peer [access control policy](/manage/access-control) with that group as the destination.
</Note> </Note>
src/pages/manage/networks/use-cases/by-scenario/cloud-to-on-premise.mdx
+1 -1
View File
@@ -189,7 +189,7 @@ Your cloud application can now securely access the on-premise database.
### High Availability ### High Availability
- Deploy multiple routing peers and configure failover - Deploy multiple routing peers and configure failover
- Monitor routing peer health with your existing tools - Monitor routing peer health with your existing tools or set up [Notifications](/manage/settings/notifications) to get alerted when a routing peer disconnects
- Use cloud-native load balancing where appropriate - Use cloud-native load balancing where appropriate
### Performance ### Performance
src/pages/manage/networks/use-cases/by-scenario/remote-worker-access.mdx
+1 -1
View File
@@ -160,7 +160,7 @@ Alternatively, create a setup key with "`remote-workers`" as an auto-assigned gr
For critical connections, consider: For critical connections, consider:
- Multiple routing peers at each location - Multiple routing peers at each location
- Monitoring routing peer health - Monitoring routing peer health via [Notifications](/manage/settings/notifications) to get alerted when a routing peer disconnects
- Automatic failover configuration - Automatic failover configuration
### Security ### Security