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
Having long node names, or many nodes or network connections, render very poorly in the pdf report graph legends. The tendency is for them to fall outside the page.
It seems to be a symptom of ggplot2 and possibly knitr page size calculation and rendering.
Examples:
Simple solutions such as trying to modify legend.margins etc. are, well, not simple.
There is a relevant discussion in the ggplot Issues over at tidyverse/ggplot2#1502, which pretty much summaries as 'making all legend combos work for all situations is very very hard'.
It would be great if we could find a 'works for all' fix for this, but it seems non trivial.
The text was updated successfully, but these errors were encountered:
Brainstorming: as we have only few nodes in scaling clusters, do you think we'd use the role of the node instead of hostname of the node in the report? For instance, if we'd just rename collectd .tar.gz files to m.tar.gz (for master) and w1.tar.gz (for the first worker etc). This would solve long hostname problem. We can include the hostnames to some tables in the PDF.
Long test names (like "pmem-off-1k-run2" in the first figure) can be considered user choice unlike hostnames.
Having long node names, or many nodes or network connections, render very poorly in the pdf report graph legends. The tendency is for them to fall outside the page.
It seems to be a symptom of ggplot2 and possibly knitr page size calculation and rendering.
Examples:
Simple solutions such as trying to modify
legend.margins
etc. are, well, not simple.There is a relevant discussion in the ggplot Issues over at tidyverse/ggplot2#1502, which pretty much summaries as 'making all legend combos work for all situations is very very hard'.
It would be great if we could find a 'works for all' fix for this, but it seems non trivial.
The text was updated successfully, but these errors were encountered: