Skip to content
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

Events create high cardinality #13

Closed
mwinters-stuff opened this issue Jun 16, 2020 · 1 comment
Closed

Events create high cardinality #13

mwinters-stuff opened this issue Jun 16, 2020 · 1 comment

Comments

@mwinters-stuff
Copy link

The events, make far too many tags, thus cardinality is extremly high - like over 200 thousand after a few prints.
Would expect cardinality to be < 50.
This affects influxdb performance, both memory and index space.

@agrif
Copy link
Owner

agrif commented Jun 21, 2020

I'm not sure why I stored those as tags -- I think it was probably the easy way out.

I've made changes to how events are stored: now, the type is stored as a tag (which it always should have been??) and the rest of the payload is stored as fields. This can result in some of the payload being dropped (if it's not a type that can be stored in a field, or if it has a datatype that changes over time) but I think it's a good first approximation.

These changes are in 1.3.0 which should be available for update now. You might want to reset your octoprint database, or at least remove the events measurement, just to clear up space.

@agrif agrif closed this as completed Jun 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants