Service Operations Insight

  • 1.  ActiveMq Data size full "5 GB" due to which alerts not updating from Domain manager

    Posted Jun 03, 2015 10:11 AM

    Hi Experts,

     

    We have installed CA SOI 3.3 in our environment and integrated with different domain managers (approx 32 domain manager), due to which we are getting huge amount of alerts around 350-400 alerts per second.

    As we are receiving such huge amount of alerts our Activemq Data size in increasing upto its limit 5 GB after which alerts are not updating in SOI but alerts are coming in different domain manager.

     

    Can any one suggest some solution to either increase  the activemq data size or any other solution.

     

    Kind Regards

    Saurabh semwal



  • 2.  Re: ActiveMq Data size full "5 GB" due to which alerts not updating from Domain manager

    Posted Jun 03, 2015 10:36 AM

    Hi,

    my suggestion to improve the situation is:

    configure your Domain Managers properly to only send Alarms that are actionable and thus should be handled by SOI.

    SOI is not an Event Console that is designed to handle every single Event - it is designed to show the impact auf faults to your Business Services.

    As such, the Alarms that reach the console should be on a level to cause an action - e.g. open a ticket, send a mail, let an Operator do something, ...

    No Operator, ticketing- or email-system can handle 350-400 "problems" per second, and thus this number should be optimized on the root level.

    MichaelBoehm



  • 3.  Re: ActiveMq Data size full "5 GB" due to which alerts not updating from Domain manager

    Posted Jun 03, 2015 10:11 PM

    Long term perm fix - Huge amout of alerts in SOI - try to optimize domain managers to report only exceptions and not just foward anything to SOI. Please share little insight about 32 domian managers and a little idea about kind of alerts they are sending up to SOI and shall post some recommendations. What kind of alerts Service impact alerts (?) or Technology alets (?)

    Incident situation resolution - Stop services flush of files under activemq-data and start services back and that should redeploy the directory. Then verify connection between SOI and connectors via netstat -abn. All connectors should come established and it should work.