# Monitoring alerts when Broker or RPC servers go down **URL:** \ **Category:** Forum\ **Tags:** Mainframe-Integration, EntireX\ **Created:** [January 7, 2015, 7:53pm UTC](https://techcommunity.softwareag.com/t/monitoring-alerts-when-broker-or-rpc-servers-go-down/180006 "2015-01-07T19:53:13Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Brian\_Johnson1](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/brian_johnson1/32/163_2.png) [@Brian\_Johnson1](https://techcommunity.softwareag.com/u/Brian_Johnson1)\ **Post date:** [January 7, 2015, 7:53pm UTC](https://techcommunity.softwareag.com/t/monitoring-alerts-when-broker-or-rpc-servers-go-down/180006/1 "2015-01-07T19:53:13Z")
Hello, I am hoping someone can share best practices on how you do alert monitoring to notify someone that a Broker or an RPC server that should be registered has gone down. Not that it happens often — SAG products are reliable — but it can and does happen for various reasons and it has a serious business impact when it does. I’d like to get that alert before a business user has to tell me through the help desk. Started tasks don’t get picked up by CA-7 either (which the Broker and Natural RPC Servers are), and Windows services on remote virtual machines are limited as well. I am hoping there are some good / best practices someone is willing to share. If I could have something that ran every 5 minutes and pinged to check to see if the Broker is up and if all the services expected are registered to it, and if not, then I can send an email and terminate with a code that command operations WILL call out for, but I don’t know a good way to do that. Or maybe there is a better idea? Thanks in advance! -Brian Johnson ---
**Author:** ![Brian\_Johnson1](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/brian_johnson1/32/163_2.png) [@Brian\_Johnson1](https://techcommunity.softwareag.com/u/Brian_Johnson1)\ **Post date:** [January 7, 2015, 8:01pm UTC](https://techcommunity.softwareag.com/t/monitoring-alerts-when-broker-or-rpc-servers-go-down/180006/2 "2015-01-07T20:01:20Z")
Ha! I might answer myself here… I see USR2073N that I will play with here to see if that works. ---
**Author:** ![Shmuel\_Coller](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/shmuel_coller/32/370_2.png) [@Shmuel\_Coller](https://techcommunity.softwareag.com/u/Shmuel_Coller)\ **Post date:** [January 7, 2015, 9:34pm UTC](https://techcommunity.softwareag.com/t/monitoring-alerts-when-broker-or-rpc-servers-go-down/180006/3 "2015-01-07T21:34:05Z")
You can use ETBINFO tool - execute every x minutes - 1. to see that Broker is up and healthy - upon normal response 2. To obtain number of RPC servers for one service You can then start additional RPC server automatically as result of this check This scripting is done at Migdal Insurance on Unix, comparable actions of mainframe EXX Broker. Shmuel ---
**Author:** ![Douglas\_Kelly](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/douglas_kelly/32/102_2.png) [@Douglas\_Kelly](https://techcommunity.softwareag.com/u/Douglas_Kelly)\ **Post date:** [February 11, 2015, 1:22am UTC](https://techcommunity.softwareag.com/t/monitoring-alerts-when-broker-or-rpc-servers-go-down/180006/4 "2015-02-11T01:22:06Z")
You can also wrap calls to the ETBCIS services for very fine-grained control over what services are being monitored. With the RPCCIS services available, this is easier to do that it used to be. ([http://techcommunity.softwareag.com/ecosystem/documentation/webmethods/wmsuites/wmsuite9-7/EntireX/9-7\_EntireX/rpc/cis-idl.htm#cis-idl](http://techcommunity.softwareag.com/ecosystem/documentation/webmethods/wmsuites/wmsuite9-7/EntireX/9-7_EntireX/rpc/cis-idl.htm#cis-idl)). Check out the scripting that is also available for monitoring: [http://techcommunity.softwareag.com/ecosystem/documentation/webmethods/wmsuites/wmsuite9-7/EntireX/9-7\_EntireX/scripting/monitorEnv.htm](http://techcommunity.softwareag.com/ecosystem/documentation/webmethods/wmsuites/wmsuite9-7/EntireX/9-7_EntireX/scripting/monitorEnv.htm) ---
**Author:** ![Brian\_Johnson1](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/brian_johnson1/32/163_2.png) [@Brian\_Johnson1](https://techcommunity.softwareag.com/u/Brian_Johnson1)\ **Post date:** [February 11, 2015, 3:33pm UTC](https://techcommunity.softwareag.com/t/monitoring-alerts-when-broker-or-rpc-servers-go-down/180006/5 "2015-02-11T15:33:47Z")
Hi Douglas, I really appreciate this information. This is the most in-depth monitoring process suggested and says it will handle ensuring RPC servers are running and not just registered with the Broker so it is ideal. We can plug this into our automated monitoring alert systems, too. This is the best-of-class solution! Regards, Brian ---
**Author:** ![system](https://global.discourse-cdn.com/techcommunity/original/3X/c/d/cd19967bb605d28a72d77eb83a1cae22f3df2eb8.svg) [@system](https://techcommunity.softwareag.com/u/system)\ **Post date:** [April 2, 2021, 3:32pm UTC](https://techcommunity.softwareag.com/t/monitoring-alerts-when-broker-or-rpc-servers-go-down/180006/6 "2021-04-02T15:32:39Z")