This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Prevent component from turning application/template red even when down

orwell8184 over 9 years ago

I am monitoring three in-house applications, AppA, AppB, and AppC. I have them in a template, AppsTemplate, that is assigned to each of the nodes I'm concerned with.
I'm interested in monitoring AppA and AppB, knowing the historical data of how often they are running, knowing what their CPU/RAM usage is, etc. However I expect AppA and AppB to go down frequently. They only run when called by AppC.

I am concerned with AppC status -- if it's up or down. I want only AppC to affect the template health. If AppA or AppB are down (and thus red) I don't want it to turn AppsTemplate red. But if AppC is red, I want it to turn AppsTemplate red.

I am pretty new to SAM. Is this possible?

Top Replies

Parents

0 Detroiter over 9 years ago

You may be better off splitting them into 2 templates, 1 with A and B, 1 with just C. You can configure an advanced alert to exclude triggering on template of A and B, but still get their metrics over time.
Cancel
Vote Up +2 Vote Down

Cancel
0 orwell8184 over 9 years ago in reply to Detroiter

That was my initial assumption and I should have put that in my post. I thought there might be a more elegant way. I will do that in the interim though, thank you!
Cancel
Vote Up 0 Vote Down

Cancel
0 aLTeReGo over 9 years ago in reply to orwell8184
Out of curiosity, are these monitors simply process/service monitors? If so, this is a open feature request that you can vote on at the below.
MONITOR PROCESSES REGARDLESS OF STATUS
Cancel
Vote Up +1 Vote Down

Cancel
0 orwell8184 over 9 years ago in reply to aLTeReGo

That feature request is exactly what we want.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 orwell8184 over 9 years ago in reply to aLTeReGo

That feature request is exactly what we want.
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 aLTeReGo over 9 years ago in reply to orwell8184

SAM 6.2 (currently in beta) allows you to monitor processes and services when they are running, and have them go into a neutral "Not Running" state when they're not. This prevents alerts from triggering and red appearing on your dashboards for processes and services that run only as-needed, while still allowing you to monitor the performance aspects of those processes and services when they are running.
Cancel
Vote Up +1 Vote Down

Cancel
0 akhasheni over 9 years ago in reply to aLTeReGo

Is there an ETA on 6.2 going out of beta?
Cancel
Vote Up 0 Vote Down

Cancel
0 aLTeReGo over 9 years ago in reply to akhasheni

It will depend upon the number of bugs found during the beta phase. Beta 3 is currently available, and a beta 4 may be available in the next few weeks.
Cancel
Vote Up +1 Vote Down

Cancel
0 akhasheni over 9 years ago in reply to aLTeReGo

Thank you. I take it, SAM can't run in "read-only" mode? (E.g. off an existing database already in use by SAM 6.1?) "Best practice" beta testing - on a separate system and DB, on a subset of existing nodes?
Cancel
Vote Up 0 Vote Down

Cancel
0 aLTeReGo over 9 years ago in reply to akhasheni

No, Orion cannot run off a read-only database. You can however backup your production database and restore it elsewhere and test the beta against that backup database.
Cancel
Vote Up +1 Vote Down

Cancel