Bug 964135
Summary: | pmchart fails to plot an archive | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Marko Myllynen <myllynen> | ||||
Component: | pcp-gui | Assignee: | Nathan Scott <nathans> | ||||
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | el6 | CC: | mgoodwin, myllynen, nathans | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2013-08-05 02:12:35 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Marko Myllynen
2013-05-17 10:49:54 UTC
Created attachment 749294 [details]
Example archives
| ... plotting csv_data_lan_both.test.lan_outbytes_linux.eth0.txbyt_s | produces an empty view It appears there is only a single value in the archive for this metric - is that expected? It also has a timestamp that is for the final fetch group in the archive. $ pmdumplog -z -a csv-data-lan-both | grep csv_data_lan_both.test.lan_outbytes_linux.eth0.txbyt_s PMID: 245.0.12 (csv_data_lan_both.test.lan_outbytes_linux.eth0.txbyt_s) 23:59:00.000 245.0.12 (csv_data_lan_both.test.lan_outbytes_linux.eth0.txbyt_s): value 657803.87 pmchart is going to have a hard time working with a single data point. Could this be a failure to import all the data you expected, Marko? (and also, is it an archive that would be susceptible to the earlier log import issues around out-of-time-order records?) thanks. As per earlier comments, on closer inspection of the archive this appears to not be a bug. Hi Nathan, yes, agreed, all the evidence suggests that this was also collateral damage of bug 958745. Thanks. |