sendnrw/netbird-docs
2
0
Fork 0
mirror of https://github.com/netbirdio/docs.git synced 2026-04-24 11:26:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

Adjust screenshots sizes (#174)

Browse Source
This commit is contained in:
juliaroesschen
2024-03-26 11:00:20 +01:00
committed by GitHub
parent a56a607923
commit 1a0f99fae7
31 changed files with 92 additions and 83 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
src/pages/how-to/monitor-system-and-network-activity.mdx
View File

@@ -10,7 +10,7 @@ Activity monitoring is enabled by default for every network, and you can access
You can also use the search bar to filter events by activity type.
<p>
<img src="/docs-static/img/how-to-guides/activity-monitoring.webp" alt="activity-monitoring" width="800" className="imagewrapper"/>
<img src="/docs-static/img/how-to-guides/activity-monitoring.webp" alt="activity-monitoring" className="imagewrapper-big"/>
</p>
<Note>
@@ -19,9 +19,11 @@ You can also use the search bar to filter events by activity type.
</Note>
<Note>
The <b>unknown</b> name or <b>unknown@unknown.com</b> e-mail address.
In the activity event store, the system keeps the deleted user information encrypted. If the encryption key has been corrupted or lost, then the events returned by the API could show "unknown@unknown.com" for the e-mail address field and "unknown" for the name field.
If the configuration files have been generated by the <b>configure.sh</b> script, you can find the previous encryption key in the backup files in the same folder as the script. Look for the <b>DataStoreEncryptionKey</b> field in the management.json backup file.
The `unknown`name or `unknown@unknown.com` e-mail address.
In the activity event store, the system keeps the deleted user information encrypted. If the encryption key has been corrupted or lost,
then the events returned by the API could show as `unknown@unknown.com` for the e-mail address field and as `unknown` for the name field.
If the configuration files have been generated by the `configure.sh` script, you can find the previous encryption key in
the backup files in the same folder as the script. Look for the <b>DataStoreEncryptionKey</b> field in the `management.json` backup file.
</Note>
## Get started