[JIRA] (JENKINS-61150) Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" needs to show JVM poolnames as well

8 views
Skip to first unread message

shashi.ptl@outlook.com (JIRA)

unread,
Feb 19, 2020, 9:45:02 AM2/19/20
to jenkinsc...@googlegroups.com
Shashidhar Addaguduru updated an issue
 
Jenkins / Bug JENKINS-61150
Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" needs to show JVM poolnames as well
Change By: Shashidhar Addaguduru
Summary: Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" should needs to show JVM poolnames as well
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

shashi.ptl@outlook.com (JIRA)

unread,
Feb 19, 2020, 9:45:03 AM2/19/20
to jenkinsc...@googlegroups.com
Shashidhar Addaguduru updated an issue
Performance Signature report data for TimeseriesIds "com.dynatrace.builtin:pgi.jvm.*" should 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
        ],

 

shashi.ptl@outlook.com (JIRA)

unread,
Feb 19, 2020, 3:40:02 PM2/19/20
to jenkinsc...@googlegroups.com
Shashidhar Addaguduru updated an issue
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.

 

shashi.ptl@outlook.com (JIRA)

unread,
Feb 19, 2020, 3:41:02 PM2/19/20
to jenkinsc...@googlegroups.com
Shashidhar Addaguduru updated an issue
Change By: Shashidhar Addaguduru
Attachment: Performance Signature report - Overall-graphs.PNG
Attachment: Performance Signature report - JVM - graphs.PNG

shashi.ptl@outlook.com (JIRA)

unread,
Feb 19, 2020, 3:41:02 PM2/19/20
to jenkinsc...@googlegroups.com
Shashidhar Addaguduru updated an issue
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.

 
Reply all
Reply to author
Forward
0 new messages