Hello
We had a connection loss to all remote agents
When the connection was rebuilt and all tests sent an email, the transmission channel was closed
How can we avoid sending an e-mail when RMA is not connected so that the transmission channel is not overloaded?
The other errors are consequential errors. Only a service restart allows for mails again.
Is it possible to reduce the connections sent to the transmission channel?
Can it be avoided that "RMA Not Connected" sends an e-mail for every Test?
We have Version 10.30 running on a Windows Server 2008R2 VM.
http://imgur.com/a/wiSKN
Errors that occured.
Screenshot: http://imgur.com/a/HM02g
=====
I have the following additional information:
We have 3337 Reviews If everyone wants to send a mail it is clear that the connection is too.
We have activated the system logging as described in the screenshot.
Http://imgur.com/a/xAh0c
Is this the correct Logfile for System Errors as SMTP Problems?
Thanks in advance
Errors after RMA Agents Connection Lost
If you have unreliable network connection on HostMonitor system, use master test to check connection
http://www.ks-soft.net/hostmon.eng/mfra ... htm#Master
If RMA agents perform many tests, then you may add master test for each agent as well.
Quote from the manual
Master0 (checks HostMontior system LAN status)
- MasterA (checks AgentA, depends on Master0)
- - test-A1 (performed by AgentA, depends on MasterA)
- - test-A2 (performed by AgentA, depends on MasterA)
- - test-A9 (performed by AgentA, depends on MasterA)
- MasterB (checks AgenBA, depends on Master0)
- - test-B1 (performed by AgentB, depends on MasterB)
- - test-B2 (performed by AgentB, depends on MasterB)
- - test-B9 (performed by AgentB, depends on MasterB)
Any errors detected by Auditing Tool (menu View)?
Do you mean "start less Send E-mail actions assigned to the tests"?
E.g. if you want to ignore all "Unknown" statuses, unmark "Treat Unknown status as Bad" option (Test Properties dialog).
But I think its better to receive some alert when agent is not accessible. You may assign different alert profiles to Master tests and "normal" tests.
Regards
Alex
http://www.ks-soft.net/hostmon.eng/mfra ... htm#Master
If RMA agents perform many tests, then you may add master test for each agent as well.
Quote from the manual
So you may setup tests likeHow to check status of the agent
When you use single agent to perform various tests, you may want to setup Master test to check agent status. In such case HostMonitor may send single alert informing you about disconnected agent and hold dependant test items (so you will receive single alert instead of hundred warnings for all tests performed by this agent).
What test can you use as Master test?
- Passive RMA: It's pretty easy to check Passive RMA status when you do not use Backup RMA. You may use TCP test to check is RMA receives connections on specified TCP port or use Ping test performed by the agent to check localhost (127.0.0.1). Such Ping test will always return "Host is alive" status when successfully authenticated connection to the agent can be established.
If there is backup agent in use, you may setup Ping test performed by Passive RMA using rma itself string as target host name. In such case HostMonitor will check agent status without using backup agent even if such backup agent was specified for selected RMA
- Active RMA: Things a little more tricky when you need to check Active RMA status. Yes, you may setup the same "Ping localhost" test to check agent status. However this may lead to some delay in reaction as HostMonitor will not perform test if agent was connected but lost connection just a moment ago. HostMonitor may wait up to several minutes for new connection before changing test status to "Unknown". Dependant test items will be delayed as well so such delay is not a big problem, you will not receive a lot of alerts. However if for some reason you need to receive alert immediately, there is solution: setup Ping test using Active RMA and type rma itself string instead of localhost or target host name. In such case HostMonitor will display agent status immediately. HostMonitor will not use backup agent (if any) when specified agent is not connected; also HostMonitor will not wait for agent re-connection.
Master0 (checks HostMontior system LAN status)
- MasterA (checks AgentA, depends on Master0)
- - test-A1 (performed by AgentA, depends on MasterA)
- - test-A2 (performed by AgentA, depends on MasterA)
- - test-A9 (performed by AgentA, depends on MasterA)
- MasterB (checks AgenBA, depends on Master0)
- - test-B1 (performed by AgentB, depends on MasterB)
- - test-B2 (performed by AgentB, depends on MasterB)
- - test-B9 (performed by AgentB, depends on MasterB)
Why exactly mail cannot be sent? What error do you see in HostMonitor system log?The other errors are consequential errors. Only a service restart allows for mails again
Any errors detected by Auditing Tool (menu View)?
Sorry, I do not understand what means "reduce the connections sent to the transmission".Is it possible to reduce the connections sent to the transmission channel?
Do you mean "start less Send E-mail actions assigned to the tests"?
Its up to you, you setup tests and actions.Can it be avoided that "RMA Not Connected" sends an e-mail for every Test?
E.g. if you want to ignore all "Unknown" statuses, unmark "Treat Unknown status as Bad" option (Test Properties dialog).
But I think its better to receive some alert when agent is not accessible. You may assign different alert profiles to Master tests and "normal" tests.
Sorry, I do not understand what this meansWe have 3337 Reviews If everyone wants to send a mail it is clear that the connection is too.
Regards
Alex
re
Hi Alex,
With the master test sounds really good.
Can you explain to me step by step how to implement this for an agent? The guide confuses me.
- the Description "ping localhost" then tests the server on which the remote agent is located or my local monitoring server?
If the ping test "tests" the remote agent itself, i can set it before all other tests.
I have already set up dependencies which the tests only run when the ping test on the remoteserver is successful.
But when the remote agent is unavailable, this seems to be different from the normal tests.
Regards
itelio
With the master test sounds really good.
Can you explain to me step by step how to implement this for an agent? The guide confuses me.
- the Description "ping localhost" then tests the server on which the remote agent is located or my local monitoring server?
If the ping test "tests" the remote agent itself, i can set it before all other tests.
I have already set up dependencies which the tests only run when the ping test on the remoteserver is successful.
But when the remote agent is unavailable, this seems to be different from the normal tests.
Regards
itelio
1) Tool bar: Add->Ping test
2) Test properties dialog: Test by: select agent
3) Test properties dialog: Address: 127.0.0.1
4) Assign some actions, Save test
4) Select all tests performed by this agent, click Edit
5) Make sure "Synchronize status&alerts" option unmarked for these tests
6) Click "add master test" button, select test created by steps 1-4
7) Keep default "perform test when master test has alive status" condition to start
8. Click Ok and Ok to close dialogs and apply changes
Also you may check "Consider status of the master test obsolete after N seconds" option (Behavior page in Options dialog)
Regards
Alex
2) Test properties dialog: Test by: select agent
3) Test properties dialog: Address: 127.0.0.1
4) Assign some actions, Save test
4) Select all tests performed by this agent, click Edit
5) Make sure "Synchronize status&alerts" option unmarked for these tests
6) Click "add master test" button, select test created by steps 1-4
7) Keep default "perform test when master test has alive status" condition to start
8. Click Ok and Ok to close dialogs and apply changes
Also you may check "Consider status of the master test obsolete after N seconds" option (Behavior page in Options dialog)
Regards
Alex
