You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have millions of metrics and we looked at tags to see if moving out instance-related nodes from metric names to tags would reduce the number of metrics and consequently also the number of whisper db files. Looks like that is not the case, as it's creating files for each metric name and tag-value combination.
So, what is the advantage of using tags over normal metrics?
The text was updated successfully, but these errors were encountered:
Indeed, tags are quite artificial for Graphite, so, not providing any significant value if using whisper as storage IMO. Compatible systems (e.g. graphite-clickhouse) using it, when not saving metric per file.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
We have millions of metrics and we looked at tags to see if moving out instance-related nodes from metric names to tags would reduce the number of metrics and consequently also the number of whisper db files. Looks like that is not the case, as it's creating files for each metric name and tag-value combination.
So, what is the advantage of using tags over normal metrics?
The text was updated successfully, but these errors were encountered: