search

spa5603 / OpsMgr.GenericServiceMonitoring

Monitor all your windows services across your entire SCOM environment out of a single spot.
GNU General Public License v3.0
2 stars 1 forks source link

Idea #1

Open Voleman opened 5 years ago

Voleman commented 5 years ago

Hi, you have wrote a cool Management Pack, thanks!

I have one idea to add to this thou. Now if I write the service name wrong to the csv, there is no error anywhere (at least I have not found it). Service just does not show up. So, could there be a log of the services that are wrong somehow? This would help a lot while I have hundreds of servicves to add to monitoring.

Also this does not work with powershell 2.0. It gives error: The PowerShell script failed with below exception

System.Management.Automation.ParseException: You must provide a value expression on the right-hand side of the '-' operator. At line:64 char:25

spa5603 commented 5 years ago

Hi, thanks for the usage of my MP. :) I appreciate your idea. I am currently working on an update of the MP which addresses exactly this problem. This update contains a rule which checks if the service is found or not. If not it generates an alert that tells you that the service was not found.

I hope i manage the release in the next weeks.

The thing with the PS 3.0 requirement will be added shortly.

Cheers

spa5603 commented 5 years ago

Hi, I have addressed all ideas in the new release. Thanks for your feedback. I appreciate that! Cheers

Voleman commented 5 years ago

Hi, I upadated this MP, but it´s not working as it should. I had 184 services dicovered earlier. Now only 65, and most of the stays "Not monitored." I have to roll to the old MP.

Regards Veli

la 12. tammik. 2019 klo 21.49 Sebastian Pabst (notifications@github.com) kirjoitti:

Hi, I have addressed all ideas in the new release. Thanks for your feedback. I appreciate that! Cheers

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/spa5603/OpsMgr.GenericServiceMonitoring/issues/1#issuecomment-453776007, or mute the thread https://github.com/notifications/unsubscribe-auth/ArSiUfGvx4PcD9b9MMMKrZu0DFspT1oXks5vCjwugaJpZM4Y1dGN .

spa5603 commented 5 years ago

That doesn't sound so good.

Please try the following to solve the problem:

  1. remove the MP completly and reimport it again to ensure a clean setup. I have made some adjustments at the discovery.

  2. If this does not help, please have a look at the "Operations Manager" log on the MS and on the client and apply a filter on the following event id "5603". You should see some error and hopefully these errors will help us to solve your problems

I hope to hear from you again.

cheers Sebastian

Voleman commented 5 years ago

I deleted the old MP and imported new one. Now it is working better and all the services were discovered. The "Service Not found" - Rule is also working, brilliant!

There is still problem with the old PowerShell version, i´m not sure if this should work in this new version or not. Also noticed that wildcard in computer name does not work. I tried it like this: servicename;computername-*;none

But altogether good job with this MP.

ke 16. tammik. 2019 klo 16.44 Sebastian Pabst (notifications@github.com) kirjoitti:

Reopened #1 https://github.com/spa5603/OpsMgr.GenericServiceMonitoring/issues/1.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/spa5603/OpsMgr.GenericServiceMonitoring/issues/1#event-2077590183, or mute the thread https://github.com/notifications/unsubscribe-auth/ArSiUXseEqwA2NC65damZHlyeTDh5OdLks5vDzrjgaJpZM4Y1dGN .

spa5603 commented 5 years ago

Thank you very much :)

I have updated the guide (readme) and powershell v3.0 is the minimum required version for the discovery script. You need to update your systems to make it work proprtly.

the csv schema is a little bit different as you think. Please update your file with the following: *servicename;;none** -> in this case the service "servicename" will be discovered on every system in your environment.

let me know if you have further problems.

cheers Sebastian

Voleman commented 5 years ago

Noticed that if service name has dot in it, it does not recognize the service, example postgresql-x64-9.4

to 17. tammik. 2019 klo 16.59 Sebastian Pabst (notifications@github.com) kirjoitti:

Thank you very much :)

I have updated the guide (readme) and powershell v3.0 is the minimum required version for the discovery script. You need to update your systems to make it work proprtly.

the csv schema is a little bit different as you think. Please update your file with the following: ;;none* -> in this case the service will be discovered on every system in your environment.

let me know if you have further problems.

cheers Sebastian

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/spa5603/OpsMgr.GenericServiceMonitoring/issues/1#issuecomment-455201483, or mute the thread https://github.com/notifications/unsubscribe-auth/ArSiUS2i9g1ca4YxYBgNikkRTTQz7Nhuks5vEI-zgaJpZM4Y1dGN .

spa5603 commented 5 years ago

thanks for another issue. I have already addressed this problem in my solution. I will release another version with this issue fixed.