WSO2 APP SERVER WEB APPLICATION STATISTICS MONITORING


Are you in need of monitoring for your web application. Need to know more details than other analytic tools provide without a cost of performance. We have the best solution. WSO2 Application Server and WSO2 Business Activity Monitor.

In current wso2 application server (AS -5.1.0) does have capability of monitoring service statistics through wso2 business activity monitor (BAM -2.2.0). But yet it does not have the ability to monitor web applications statistics

In the next AS release (5.2.0) we have integrated the capability of monitoring web application statistics with BAM (2.3.0)

You may  follow the steps mentioned below to activate the monitoring.

Please download AS from here and BAM from here.


CONFIGURING APP SERVER.

  1. To start the AS you have to follow the steps below.
    • Go to {AS_HOME}/repository/conf/ and open carbon.xml
    • Look for <offset>0</offset> and change it 1.
    • Go to {AS_HOME}/repository/conf/etc/ and open bam.xml.
    • Look for <WebappDataPublishing>disable</WebappDataPublishing> and enable it.
    • Then go to {AS_HOME}/bin and run wso2server.sh if you are in linux, wso2server.bat if you are in windows.
    • Then log in to AS management console and go to Configure > Webapp Data Publishing. (Note If you are on tenant, you have to configure this separately.)
    • Tick the "Enable webapp stats" and fill the relevant details.

    • Leave the Stream Name, Version, Nick Name, Description as it is. If you need to change them you will have to make some more changes in the tool box and hive script. Which will be discussed later.
      • Receiver URL - Thrift url, This is normally tcp://{host}:7611, If you need to use SSL for this you tcps://{host}:7711. (If you change the offset of BAM server to 1 both port will be incremented by 1 (7612, 7712)
      •  Username - Cassandra user name 
      • Password - Cassandra Password
Now you have successfully configured AS for Data publishing to BAM. Now we need to configure in AS which web applications needs monitoring and which does not. For that before you deploy a web application, another change has to be done to web.xml or you can enable it by web app dash board.


 Please click on the check box given to enable bam web app statisitic monitoring for relevant web application.

Or you can add the following context params to application web.xml. Please note that ui has the precedence over web.xml configurations. It means that if you disable web apps statics monitoring from ui, configurations in web.xml will not work.

      <context-param>
             <param-name>enable.statistics</param-name>
             <param-value>true</param-value>
      </context-param>

If you deploy any web application with above parameters included in the web.xml or enabled from ui, AS is ready to publish the data to BAM.


CONFIGURING BUSINESS ACTIVITY MONITOR


  1. Start the BAM server  - Go to {BAM_HOME}/bin, and run wso2server.sh if you are in linux, wso2server.bat if you are in windows. (If you need to change  databases which stores statistic data, please create database and configure it in {BAM_HOME}/repository/conf/datasources/master-datasources.xml  as  WSO2BAM_DATASOURCE, If you have changed the portoffset you have to change cassandra port in WSO2BAM_CASSANDRA_DATASOURCE.)
  2. Go to Home > Manage > BAM Toolbox > Add and look for WebApps_Stats_Monitoring tool box. and click install. Please refresh the after few seconds to see weather tool is installed.
  3. Send few request from AS (Invoke any web applications which has enabled statistics monitoring.
  4. Go to Home > Manage > Analytics > List and find webapp_statistics, execute it or schedule it running sequence.
  5. Go to Dashboard and login with admin/admin  you can view following details from ui
  • All request summary - (All / Month / Day / Now)



    1. Request count
    2. Response count
    3. Error count
    4. Average response time
    5. Minimum Response Time
    6. Maximum Response Time
    7. Number of user visits (Amount of users, web app used.)
    8. Average length time of user visits (average session time)
    9. Page visits
  • Per tenant request summary – (All / Month / Day / Now)



    1. Request count
    2. Response count
    3. Error count
    4. Average response time
    5. Minimum Response Time
    6. Maximum Response Time
    7. Number of user visits (Amount of users, web app used.)
    8. Average length time of user visits (average session time)
    9. Page visits
  • Per web app request summary – (All / Month / Day / Now)



    1. Request count
    2. Response count
    3. Error count
    4. Average response time
    5. Minimum Response Time
    6. Maximum Response Time
    7. Number of user visits (Amount of users, web app used.)
    8. Average length time of user visits (average session time)
    9. Page visits.



Request Count and Average Response Time



Average Response Time and Request/Response/Fault Count



Number of User Visits and Average Length of User Visits






Comments

Post a Comment

Popular posts from this blog

WSO2 ESB Removing full soap header using enrich mediator.

WSO2 ESB supports many mediators, and we can use them to achieve most of our use cases. The following message template illustrates the structure of a SOAP Envelope: <soap:Envelope   xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">   <soap:Header> <!-- optional -->     <!-- header blocks go here... -->   </soap:Header>   <soap:Body>     <!-- payload or Fault element goes here... -->   </soap:Body> </soap:Envelope> Even though soap header is optional, you might receive the soap envelop with soap headers. And you might need to remove the soap header element including <soap:Header></soap:Header> element. You can achieve this by using enrich mediator and payload factory mediator. We first extract the body from the soap envelop and assign it to a property using enrich mediator. Then we create an empty soap envelop using payload factory. At last enrich mediator is again used to put the soap b
Read more

Getting started with WSO2 Device Cloud APIs

Image
Introduction WSO2 Device Cloud is the latest addition to WSO2’s Cloud offering. It aims to provide device integration and management to rest of the WSO2 cloud. As of now, it allows integrating and managing Android & iOS powered devices. Device Cloud offers an UI to manage connected devices. Fig 1: Device Management Dashboard Page on Device Cloud Fig 2: Listing of all registered devices But the functionality is not limited to a web application. All device management capabilities are offered as OAuth2 protected REST APIs as well.   This tutorial explains how to make programmatic use of these APIs. In order to proceed with examples, you need to have a WSO2 Cloud account ( https://cloud.wso2.com ).  If you do not possess an account please use the following url to register one. https://cloudmgt.cloud.wso2.com/cloudmgt/site/pages/index.jag   API Store All apis related to device management are available in the API Store part of WSO2 Cloud. https://api.
Read more

Running a Standalone WSO2 IoT Server.

WSO2 IoT Server  can be run on single instance with simple configurations.  WSO2 IoT server  consists of 3 major services. IoT Core — This service includes all the major device management capabilities such as operation, policy management etc. It also includes the security and API management capabilities. Analytics — This service includes components for data gathering and analysis in both real-time and batch. It also includes the capability to do machine learning as well complex event processing and fraud detection. Broker — This service acts as the message exchanger between server and devices. By default, WSO2 IoT server uses OAuth as the security mechanism. When a user login into the devicemgt user interface, it uses the OAuth token to validate the user in the underlying infrastructure. It supports few OAuth grant types and by default devicemgt application user the JWT token grant type. And by default WSO2 IoT Server runs as with the hostname as localhost. If you do not
Read more