-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Performance Signature plugin version 3.1.0
Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" needs to show JVM poolname values as well. The Dynatrace API response json (sample) contains datapoint "poolname" in addition to PGI name as seen in below response JSON.
Currently the same PGI name displaying under each of the rows on the corresponding data table on the Signature report and it is not possible to identify which poolname the row data belongs to.
"dataResult": {
"dataPoints": {
"PROCESS_GROUP_INSTANCE-B63C48A933CE7D72, pid=0x1, poolname='PS Eden Space'": [
[
1582042260000,
17256976
],
[
1582042320000,
24354080
],
Might be due to this discrepancy, the data on the graphs are not reflecting the data in the tables. The graphs of all poolnames are showing same data. Attached screenshot for this issue.
Another issue is that the data on Overall graphs under all TimeseriesIds are not reflecting the data under the Overall row data. Attached screenshot for this issue.
[JENKINS-61150] graphs data do not reflect the actual data shown under the data tables on the Performance Signature report
Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
Description |
Original:
Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" should show JVM poolname values as well. The API response json contains datapoint "poolname" in addition to PGI name as seen in below response JSON. Currently the same PGI name displaying under each of the rows on the corresponding data table on the Signature report and it is not possible to identify which poolname the row data belongs to. "dataResult": { "dataPoints": { "PROCESS_GROUP_INSTANCE-B63C48A933CE7D72, pid=0x1, poolname='PS Eden Space'": [ [ 1582042260000, 17256976 ], [ 1582042320000, 24354080 ], |
New:
Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" should show JVM poolname values as well. The Dynatrace API response json contains datapoint "poolname" in addition to PGI name as seen in below response JSON. Currently the same PGI name displaying under each of the rows on the corresponding data table on the Signature report and it is not possible to identify which poolname the row data belongs to. "dataResult": { "dataPoints": { "PROCESS_GROUP_INSTANCE-B63C48A933CE7D72, pid=0x1, poolname='PS Eden Space'": [ [ 1582042260000, 17256976 ], [ 1582042320000, 24354080 ], |
Summary | Original: Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" should show JVM poolnames as well | New: Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" needs to show JVM poolnames as well |
Description |
Original:
Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" should show JVM poolname values as well. The Dynatrace API response json contains datapoint "poolname" in addition to PGI name as seen in below response JSON. Currently the same PGI name displaying under each of the rows on the corresponding data table on the Signature report and it is not possible to identify which poolname the row data belongs to. "dataResult": { "dataPoints": { "PROCESS_GROUP_INSTANCE-B63C48A933CE7D72, pid=0x1, poolname='PS Eden Space'": [ [ 1582042260000, 17256976 ], [ 1582042320000, 24354080 ], |
New:
Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" needs to show JVM poolname values as well. The Dynatrace API response json contains datapoint "poolname" in addition to PGI name as seen in below response JSON. Currently the same PGI name displaying under each of the rows on the corresponding data table on the Signature report and it is not possible to identify which poolname the row data belongs to. "dataResult": { "dataPoints": { "PROCESS_GROUP_INSTANCE-B63C48A933CE7D72, pid=0x1, poolname='PS Eden Space'": [ [ 1582042260000, 17256976 ], [ 1582042320000, 24354080 ], |
Description |
Original:
Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" needs to show JVM poolname values as well. The Dynatrace API response json contains datapoint "poolname" in addition to PGI name as seen in below response JSON. Currently the same PGI name displaying under each of the rows on the corresponding data table on the Signature report and it is not possible to identify which poolname the row data belongs to. "dataResult": { "dataPoints": { "PROCESS_GROUP_INSTANCE-B63C48A933CE7D72, pid=0x1, poolname='PS Eden Space'": [ [ 1582042260000, 17256976 ], [ 1582042320000, 24354080 ], |
New:
Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" needs to show JVM poolname values as well. The Dynatrace API response json contains datapoint "poolname" in addition to PGI name as seen in below response JSON. Currently the same PGI name displaying under each of the rows on the corresponding data table on the Signature report and it is not possible to identify which poolname the row data belongs to. "dataResult": { "dataPoints": { "PROCESS_GROUP_INSTANCE-B63C48A933CE7D72, pid=0x1, poolname='PS Eden Space'": [ [ 1582042260000, 17256976 ], [ 1582042320000, 24354080 ], Might be due to this discrepancy, the data on the graphs are not reflecting the data in the tables. The graphs of all poolnames are showing same data. Attached screenshot for this issue. Another issue is that the data on Overall graphs under all TimeseriesIds are not reflecting the data under the Overall row data. Attached screenshot for this issue. |
Attachment | New: Performance Signature report - Overall-graphs.PNG [ 50352 ] | |
Attachment | New: Performance Signature report - JVM - graphs.PNG [ 50353 ] |
Description |
Original:
Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" needs to show JVM poolname values as well. The Dynatrace API response json contains datapoint "poolname" in addition to PGI name as seen in below response JSON. Currently the same PGI name displaying under each of the rows on the corresponding data table on the Signature report and it is not possible to identify which poolname the row data belongs to. "dataResult": { "dataPoints": { "PROCESS_GROUP_INSTANCE-B63C48A933CE7D72, pid=0x1, poolname='PS Eden Space'": [ [ 1582042260000, 17256976 ], [ 1582042320000, 24354080 ], Might be due to this discrepancy, the data on the graphs are not reflecting the data in the tables. The graphs of all poolnames are showing same data. Attached screenshot for this issue. Another issue is that the data on Overall graphs under all TimeseriesIds are not reflecting the data under the Overall row data. Attached screenshot for this issue. |
New:
Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" needs to show JVM poolname values as well. The Dynatrace API response json (sample) contains datapoint "poolname" in addition to PGI name as seen in below response JSON. Currently the same PGI name displaying under each of the rows on the corresponding data table on the Signature report and it is not possible to identify which poolname the row data belongs to. "dataResult": { "dataPoints": { "PROCESS_GROUP_INSTANCE-B63C48A933CE7D72, pid=0x1, poolname='PS Eden Space'": [ [ 1582042260000, 17256976 ], [ 1582042320000, 24354080 ], Might be due to this discrepancy, the data on the graphs are not reflecting the data in the tables. The graphs of all poolnames are showing same data. Attached screenshot for this issue. Another issue is that the data on Overall graphs under all TimeseriesIds are not reflecting the data under the Overall row data. Attached screenshot for this issue. |
Summary | Original: Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" needs to show JVM poolnames as well | New: graphs data do not reflect the actual data shown under the data tables on the Performance Signature report |