Updates to Github #github
Pcp Integration <[email protected]>
| Newsgroups | gmane.comp.sysutils.pcp |
|---|---|
| Message-ID | <[email protected]> |
[pcp:master] New Issue Created by fche ( https://github.com/fche ) : #270 boolean / quantified operations for derived-probes ( https://github.com/performancecopilot/pcp/issues/270 ) It would be nice to be able to express pmie-like boolean expressions in the derived-metric language, so that timelines can be constructed of the true/false values. pmdasummary, being systemwide, is not a good substitute. The minimum would probably be language extensions for: - boolean operators (> == < etc.) - quantification over instances (any(x) all(x) none(x)) - type/scale conversion operator (e.g., convert(x, "kbytes/hour")) - maybe, historical-value operator (@0 etc., recast into functional notation?) - maybe, accept floating point literals, not just integers --- [pcp:master] New Issue Created by fche ( https://github.com/fche ) : #270 boolean / quantified operations for derived-probes ( https://github.com/performancecopilot/pcp/issues/270 ) It would be nice to be able to express pmie-like boolean expressions in the derived-metric language, so that timelines can be constructed of the true/false values. pmdasummary, being systemwide, is not a good substitute. The minimum would probably be language extensions for: - boolean operators (> == < etc.) - quantification over instances (any(x) all(x) none(x)) - type/scale conversion operator (e.g., convert(x, "kbytes/hour")) - maybe, historical-value operator (\@0 etc., recast into functional notation?) - maybe, accept floating point literals, not just integers --- [pcp:master] New Issue Created by fche ( https://github.com/fche ) : #270 boolean / quantified operations for derived-metrics ( https://github.com/performancecopilot/pcp/issues/270 ) It would be nice to be able to express pmie-like boolean expressions in the derived-metric language, so that timelines can be constructed of the true/false values. pmdasummary, being systemwide, is not a good substitute. The minimum would probably be language extensions for: - boolean operators (> == < etc.) - quantification over instances (any(x) all(x) none(x)) - type/scale conversion operator (e.g., convert(x, "kbytes/hour")) - maybe, historical-value operator (\@0 etc., recast into functional notation?) - maybe, accept floating point literals, not just integers