From 0506de948e39b2922dc11a3fcd9ccbc5c98f7af1 Mon Sep 17 00:00:00 2001 From: Zoltan Papp Date: Tue, 17 Oct 2023 12:15:33 +0200 Subject: [PATCH] Broken event store key (#106) * Add broken event store key description * Fix grammar --------- Co-authored-by: Zoltan Papp --- src/pages/how-to/monitor-system-and-network-activity.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/src/pages/how-to/monitor-system-and-network-activity.mdx b/src/pages/how-to/monitor-system-and-network-activity.mdx index 840f27c2..df95b191 100644 --- a/src/pages/how-to/monitor-system-and-network-activity.mdx +++ b/src/pages/how-to/monitor-system-and-network-activity.mdx @@ -18,6 +18,12 @@ You can also use the search bar to filter events by activity type. The future versions will support connection events that occur in NetBird agents (e.g., peer A connected to peer B). + + 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 "unknown@unknown.com" for the e-mail address field and "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 DataStoreEncryptionKey field in the management.json backup file. + + ## Get started