New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve dbengine docs for streaming setups #9177
Conversation
Manage this branch in SquashTest this branch here: https://joelhansdbengine-tweaks-hmi6z.squash.io |
database/engine/README.md
Outdated
mode** that supports changing the data collection update frequency (`update_every`) **without losing** the previously | ||
stored metrics. | ||
The Database Engine works like a traditional database. It dedicates a certain amount of RAM to data caching and | ||
indexing, while and the rest of the data resides compressed on disk. Unlike other [database modes](/database/README.md), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
while the rest
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
database modes
-> memory modes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed both of these (and the rest of yours, @zack-shoylev)!
database/engine/README.md
Outdated
The Database Engine works like a traditional database. It dedicates a certain amount of RAM to data caching and | ||
indexing, while and the rest of the data resides compressed on disk. Unlike other [database modes](/database/README.md), | ||
the amount of historical metrics stored is based on the amount of disk space you allocate and the effective compression | ||
ratio, not a fixed number of history entries. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed number of metrics collected.
When the disk quota is exceeded the oldest values are removed from the DB engine at real time, by automatically deleting | ||
the oldest datafile and journalfile pair. Any corresponding pages residing in the Page Cache will also be invalidated | ||
and removed. The DB engine logic will try to maintain between 10 and 20 file pairs at any point in time. | ||
The Agent allocates resources for each instance separately using the `dbengine disk space` setting. If `dbengine disk |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i would copy that to the calculator also
database/engine/README.md
Outdated
location is `/var/cache/netdata/dbengine/*`). The higher numbered filenames contain more recent metric data. The user | ||
can safely delete some pairs of files when Netdata is stopped to manually free up some space. | ||
|
||
_Users should_ **back up** _their `./dbengine` folders if they consider this data to be important._ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's add a link to exporters as well as an alternative
* Refactor dbengine and add streaming section * Tweaks and copyediting * Fixes for Zack and Markos
Summary
Fixes part of #9106. The other work is at netdata/learn#159.
I came into the dbengine doc to make a few tweaks around multiple instances and streaming configs, but ended up doing a bit more refactoring. The primary goal here is to help users understand that in streaming setups, the dbengine uses separate instances for each node, despite sharing the same
page cache size
anddbengine disk space
settings.Component Name
agent/database
Test Plan
Additional Information