Skip to content

Commit

Permalink
chore: add link to telemetry page
Browse files Browse the repository at this point in the history
  • Loading branch information
Benmuiruri committed Nov 28, 2023
1 parent 119ddb5 commit a3d0ff3
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion content/en/apps/concepts/navigation.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ Synchronization consists of upward replication and downward replication.
The CHT application manages data synchronization across two types of databases: the main application database and a meta database.

- **Main Application Database (`medic`)**: The main database that stores the primary data used by the application. It includes contacts, reports, messages, and other critical documents necessary for the core functionality of the application. This database is synchronized continuously to reflect changes to the application, such as new contact creations. Each user stores a subset of the main database which includes only the documents they're allowed to view.
- **User-Metadata Database(`medic-user-{username}-meta`)**: Each user has a dedicated database that stores operational metadata, including telemetry data such as reading a report. Synchronization occurs at predefined intervals to ensure up-to-date monitoring and analysis.
- **User-Metadata Database(`medic-user-{username}-meta`)**: Each user has a dedicated database that stores operational metadata, including [telemetry data]({{< relref "apps/guides/performance/telemetry" >}}) and error messages. Synchronization occurs at predefined intervals to ensure up-to-date monitoring and analysis.

The CHT application has two different Sync Intervals:
- **Regular Sync**: Occurs every 5 minutes. It replicates application data, including user-generated content and any changes to existing documents.
Expand Down

0 comments on commit a3d0ff3

Please sign in to comment.