Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Analysis of the reports/dashboards/analytics #10

Closed
fcorti opened this issue Dec 30, 2015 · 14 comments
Closed

Analysis of the reports/dashboards/analytics #10

fcorti opened this issue Dec 30, 2015 · 14 comments
Assignees

Comments

@fcorti
Copy link
Collaborator

fcorti commented Dec 30, 2015

Which dashboards can/should be defined?
Which reports can/should be defined?
Which analytics can/should be defined?
About reports/analytics: how to release them in the crystal installation?

@fcorti
Copy link
Collaborator Author

fcorti commented Jan 2, 2016

The very first dashboard is an high view of the tests available.
Below an image of the committed version (few minutes ago).

schermata 2016-01-02 alle 19 42 13

Now it's time to think about other dashboards, more detailed and dedicated to specific business questions.

@fcorti
Copy link
Collaborator Author

fcorti commented Jan 4, 2016

Added a dashboard that details the raw logs with filter on test and period (date only) and CSV/XLS export feature.

schermata 2016-01-04 alle 08 17 11

@lcabaceira
Copy link
Owner

Nice one, i'm going to give it a try later and provide feedback.

@lcabaceira
Copy link
Owner

I've updated both test cases (share automation and cmis tests) to generate reports on the correct folder and with the recommended pentaho friendly format.

@lcabaceira
Copy link
Owner

We should change the pentaho port to 9090 or other than 8080. People that are testing Crystal tend to have a local installation of Alfresco in 8080 and that conflicts with pentaho port. Is it just a matter of changing the tomat server.xml to listen on 9090 instead or we need to change it somewhere else ?

@fcorti
Copy link
Collaborator Author

fcorti commented Jan 15, 2016

No problem.
This week has been crazy in the office.
During the weekend I'll change the port and check the issues.

@fcorti
Copy link
Collaborator Author

fcorti commented Jan 16, 2016

Ok, Pentaho ports changed to 8080, 9009, 9443.
To answer to your question: yes, it is a matter to change the server.xml config file.

@lcabaceira
Copy link
Owner

You mean 9090,9009,9443 :) ?

@fcorti
Copy link
Collaborator Author

fcorti commented Jan 18, 2016

Ops... yes, 9090, 9009, 9443.
Updated also the documentation: https://github.com/lcabaceira/crystal/wiki

@lcabaceira
Copy link
Owner

The reports we need for now, that we already have inside jmeter and their data is already being exported are as follow :

  • Response times over time
  • Transactions per second
  • Active threads over time
  • Hits per second
  • Heap Memory
  • Cpu Usage
  • Garbage collector CMS (Collection Count/Collection Time)
  • Garbage collector ParNew (Collection Count/Collection Time)
  • Tomcat Threads HTTP (8080)
  • Tomcat Threads HTTPS (8443)
  • Tomcat Threads HTTPS (8009)
  • Concurrent Users/Concurrent Tickets

I can attach the diagrams created by jmeter if those help.

@fcorti
Copy link
Collaborator Author

fcorti commented Jan 20, 2016

I'm going on this path...

Active threads over time is quite ready.
Response times over time is quite ready.

The others will come... stay tuned.

@fcorti
Copy link
Collaborator Author

fcorti commented Jan 24, 2016

Added the first draft of the reports below:

  • Response times over time
  • Transactions per second
  • Active threads over time
  • Hits per second

Before going ahead with the other reports, need to refine the ETL to recognize of the data regard the results or the JMXs.
Then filter and refine the results in the charts.

@fcorti
Copy link
Collaborator Author

fcorti commented Jan 25, 2016

ETL refined!
Now a TYPE field ha been added to the Data Mart and reports filter on this field.
Let's work on the other reports...

@fcorti
Copy link
Collaborator Author

fcorti commented Jan 31, 2016

All the available reports in JMeter are developed.
Of course need to be deeply tested.

dashboard

@fcorti fcorti closed this as completed Jan 31, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants