3 Replies Latest reply on Jun 4, 2012 12:32 PM by jay shaughnessy

    RHQ Choice ?

    Tarun .. Newbie

      Dear All,


      I want to use RHQ for monitoring certain machines.( I have used RHQ before and its a great product, thats the reason I have come back to RHQ)

      Earlier DB size was not such a requirement for me but now it is..

      The question i have is : I understand there is requirement for backend database while using RHQ.

      So, are all the metrics data that is collected by agents and then sent to RHQ server, is all of this data stored in database ?

      If yes, then eventually the size of data in DB would increase over a period of time ?


      As I want to use RHQ for (near-realtime )monitoring purpose , I dont want to store this metric data in DB .


      As If i have several Client PC's (Agents) giving measurement data, there will be a lot of data in DB.


      If at all the data is stored in DB, is there an automated mechanism to remove this data ?


      Your help would be much appreciated !




        • 1. Re: RHQ Database requirement ?
          Lukas Krejci Apprentice

          The metric data in the database is "compressed" and purged for exactly the reasons you describe. As the metric data gets "older", the datapoints are "collapsed" into 1hour, 6hour and 24hour "buckets" (each bucket maintaining only the min, max and average of the original data). This way we limit the raw size of the data to store. Additionally  we purge metric data older than 2 years (i think).


          Also, because you mention "near real-time monitoring" - I'd like to urge you to do very rigorous testing of your deployment before you go live with it. Even though we try hard to be as efficient when storing metric data into the database as possible, it has been a known performance bottleneck of RHQ. So you have to weigh the amount of metric data coming into the database with the size of your inventory and actual functional requirements you have on the monitoring.


          Hope this helps,



          • 2. Re: RHQ Database requirement ?
            Tarun .. Newbie

            Dear Lukas,


            Thanks for your answer ! I want to know I can customize the data purging option in database under 3 days or less ?

            Also you mentioned there have been some performance bottlenecks, can you give an example of such bottleneck ?


            Well in my case there are will be around 2000 Agents (or client PC) whhich have to be monitored.

            I assume this is will put a huge load on the server , right ? Can you please suggest if it is feasiable to use RHQ for this case, where clients PCs are around 2000 ?


            Your anwer helped, awaiting someone reply on this.




            • 3. Re: RHQ Database requirement ?
              jay shaughnessy Expert

              That is a very large installation.  As Lukas mentions, you should definitely stage this and add in agents incrementally.  It will require a significant database backend and tight control over the metrics being collected.  Note that RHQ will not allow metric collection at intervals less than 30s, so that may affect your need for near-real time monitoring.


              For that number of clients you will likely want several servers, look in the documentation for High Availability configurations.  Note that multiple servers will still funnel all data to a single backend database, so it must be configured for adequate numbers of connections and with tablespaces adequate for the load.


              You can customize purge times to some degree.  Look in Administration system settings.


              I am not sure there are any RHQ installations with that number of agents, perhaps anyone else with a large installation can comment.