Bug 1133063
| Summary: | Globally uncaught exception - on metrics if we expand metric chart under metrics | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | Jeeva Kandasamy <jkandasa> | ||||
| Component: | Storage Node | Assignee: | Mike Thompson <mithomps> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Mike Foley <mfoley> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | JON 3.2.3 | CC: | loleary, mithomps | ||||
| Target Milestone: | --- | ||||||
| Target Release: | JON 3.3.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-08-27 20:43:10 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: |
|
||||||
To further clarify, this bug only exists on a newly enabled schedule and exists only for the collection interval amount. For instance, if 'JVM Free Memory' is enabled and it has a collection interval of 20 minutes then no data is collected until 20 minutes and the Globally uncaught exception is thrown until a metric value is collected according to the metric schedule. Correction, to the above statement. It only exists for < 1 minute. Not for the full collection interval amount as stated above. It takes a small amount of time to start receiving metrics not the collection interval amount. In previous releases a metric value could be NaN to represent that a metric was collected but was not a valid value. This could occur in situations like a trends up value was returned but does not represent a valid value as the underlying statistic has not yet been populated. I am not sure if this still applies but I haven't seen any indication that such behavior had changed. In which case we should probably decide how such values should impact the graph. Seems like the values would just be thrown out -- in the same manner as if they just weren't collected -- but I am not sure why NaN would have been used then. In any case, I think that if all values are NaN -- min, max, and average -- it would make sense to display a blank graph area with text saying 'no available data for period' or something similar. If on the other hand at least one value is available -- min, max, or average -- we should attempt to graph a reasonable aggregate or normalized value. |
Created attachment 929681 [details] metrics exception Description of problem: Globally uncaught exception - on metrics if we expand metric (with NaN value) chart under metrics. After enabled some schedule under 'Schedules' navigate to 'Metrics', Click expand arrow which has NaN value. Throws "Globally uncaught exception" Version-Release number of selected component (if applicable): JBoss Operations Network Version : 3.2.0.GA Update 03 Build Number : bca1bc8:e19c43d GWT Version : 2.5.0 SmartGWT Version : 3.0p How reproducible: always Steps to Reproduce: 1. Navigate to 'Monitoring->Schedules' of any resource (ex: RHQ Agent) 2. Enable some schedule, navigate to 'Metrics' page 3. Expand the metric the we enabled on setp #2 4. Throws "Globally uncaught exception" 5. Other way to produce this issue, on the 'Metrics' click time line for 3 months or 6 months, you can see metrics with NaN value. Expand the metric. Throws exception. Actual results: Throws Exception Expected results: should not throw exception. Additional info: screen shot is attached.