aparna.valsala

How did I miss this for so long!!! Voted Up.. Up and Up

Much needed, please bring it soon

As always - Wonderful, Josh

Bumping Again!!!

Try something like this

In the last exit, do not do a exit $status, rather return a numeric value, something like exit(0) or exit(1), let me know if that worked.

LOL I miss the days there

Hmm.. you can disable them and re-enable them once the work on them is over. Unfortunately we cannot Un-manage/disable them for a pre-defined duration at component level.

I tested it in our dev too that runs on SAM 6.4, thinking it might be my prod/website, same issue there too. And I also checked whether we have it for node management too and that looks ok.

I have rebuilt the performance counters using lodctr /R already, that did not help me. I have also rebuilt the .Net performance counters, no luck with that as well.

Thanks Vinay It was wonderful to work with you and ofcourse learn from you too! Missing those days

Hi Sakshi, You can do it this way * Write your PowerShell script and call it from a batch file from your primary polling engine * Go to Alert Manger * Navigate to Trigger Actions * Select execute an external program. * <path>\batchfile.bat "${N=SwisEntity;M=Application.Node.IP_Address}" (this variable is for a component…

Its wonderful that when I look for some solution on Thwack, I find solutions from your posts jbiggley​ Thanks a ton for all the learnings

The following docs would be of help if you are looking for a list of items that "can" be monitored by SAM: Server & Application Monitor Template Reference Component Monitor Types

You can disable the component instead.

Easiest way to do it is name the component(s) as the URL(s) itself, then you can create a report for Components with Component type = HTTP Monitor OR HTTPS Monitor

They have to be a part of Application Monitor template. Refer Understand component monitors and application monitor templates to understand these terminologies better.

Thanks Josh, I have been searching for something similar

Try this .. create a batch file in your primary polling engine that would accept affected Node IP Address (better than caption) as an argument, have it call your powershell script in which you may pass the same IP Address so that it knows which server to clean up. From the alert action, execute an external program, you can…