No data in RUM Session Summary and Session Analyzer Reports

Hi Team,

 

We have put an application  into monitoring using HPRUM.  But we are not getting any data for the application in below two reports

 

- Session Analyzer

- Session Summary

 

Error that we recieve while generating these reports are as below

 

"'There was a problem in retrieving data from the RUM engines""

 

 

Please note that rest all reports(RUM tier summary, RUM Action summary, RUM Transaction summary) reports are having their respective data available.

 

Please help in knowing how we can resolve this issue

 

Thanks & Regards

Lini

 

 

Parents
  • Hi Lini,

     

    for most reports BSM takes the data out of the BSM profile database, for 

    - Session Analyzer

    - Session Summary

    it talks to the RUM Engine and retrieves the data from the RUM MySQL database.

    If this fails, you'll see the message  

    "'There was a problem in retrieving data from the RUM engines""

     

    Have a look at <BSM>\log\EJBContainer\gde.ejb.log to check for obvious errors AFTER running one of the failing report.

    The issue can be as easy as the BSM server being unable to resolve the engine hostname and can be as complex as a corrupt MySQL database.

    If you cannot find anything obvious in that logfile, enable GDE debug logging by modifying the file

    <BSM>\conf\core\Tools\log4j\EJBGDE.properties

    change

    loglevel=ERROR

    to
    loglevel=DEBUG

    save the changes, wait 2 minutes, then run the failing report again and then check the logfile again.

    If you fail to find the reason for the error, post the logfile here for a look.

     

    Greetings

    Siggi

Reply
  • Hi Lini,

     

    for most reports BSM takes the data out of the BSM profile database, for 

    - Session Analyzer

    - Session Summary

    it talks to the RUM Engine and retrieves the data from the RUM MySQL database.

    If this fails, you'll see the message  

    "'There was a problem in retrieving data from the RUM engines""

     

    Have a look at <BSM>\log\EJBContainer\gde.ejb.log to check for obvious errors AFTER running one of the failing report.

    The issue can be as easy as the BSM server being unable to resolve the engine hostname and can be as complex as a corrupt MySQL database.

    If you cannot find anything obvious in that logfile, enable GDE debug logging by modifying the file

    <BSM>\conf\core\Tools\log4j\EJBGDE.properties

    change

    loglevel=ERROR

    to
    loglevel=DEBUG

    save the changes, wait 2 minutes, then run the failing report again and then check the logfile again.

    If you fail to find the reason for the error, post the logfile here for a look.

     

    Greetings

    Siggi

Children