This app supplies the functionality for the
When a database is created, deleted, or updated, a corresponding event will be persisted to disk (Note: This was designed without the guarantee that a DB event will be persisted or ever occur in the
_db_updates feed. It probably will, but it isn't guaranteed). Users can subscribe to a
_changes-like feed of these database events by querying the
When an admin user queries the
/_db_updates endpoint, they will see the account name associated with the DB update as well as update
db_writes: The number of doc updates caused by global_changes.
server_pending_updates: The number of documents aggregated into the pending write batch.
listener_pending_updates: The number of documents aggregated into the pending event batch.
event_doc_conflict: The number of rev tree branches in event docs encountered by global_changes. Should never happen.
rpcs: The number of non-fabric RPCs caused by global_changes.
max_event_delay: (integer, milliseconds) The total timed added before an event is forwarded to the writer.
max_write_delay: (integer, milliseconds) The time added before an event is sent to disk.
update_db: (true/false) A flag setting whether to update the global_changes database. If false, changes will be lost and there will be no performance impact of global_changes on the cluster.