{"id":410,"date":"2021-12-23T19:20:13","date_gmt":"2021-12-23T18:20:13","guid":{"rendered":"http:\/\/www.gerjon.com\/?p=410"},"modified":"2021-12-23T19:24:46","modified_gmt":"2021-12-23T18:24:46","slug":"receive-alerts-from-your-vmware-environment-in-microsoft-teams","status":"publish","type":"post","link":"https:\/\/www.gerjon.com\/?p=410","title":{"rendered":"Receive alerts from your VMware environment in Microsoft Teams"},"content":{"rendered":"\n

Problem<\/strong><\/span><\/p>\n\n\n\n

When you have your own (VMware) Lab you don’t always have time to look at the state of the lab and if ‘all lights are in the green’ so to say. So how cool would it be to be alerted on your phone if a problem would occur on your test environment. But monitoring the environment from inside the environment is always tricky because if its down its not alerting \ud83d\ude42<\/p>\n\n\n\n

Solution<\/strong><\/span><\/p>\n\n\n\n

After some searching on the internet I decided to monitor my vSphere environment via a and Raspberry Pi 3 I had laying around with Raspberry Pi OS installed on it. In case of an error there should be a notification popup in a Microsoft Teams channel. <\/p>\n\n\n\n

So that’s the theory. Lets see if we can get it to work.<\/p>\n\n\n\n

Configuring the alerting<\/strong><\/p>\n\n\n\n

So i have a MSDN subscription for Office 365 and also access to teams in this subscription so what I did wat create a separate team for the alert (you can also get this into a channel in an existing team but for me this was a better separation. I used the web version of teams but you could also use the desktop version.<\/p>\n\n\n\n

\"\"
First add a channel to an existing (or new) teams site.<\/figcaption><\/figure>\n\n\n\n
\"\"
Give it a cool name \ud83d\ude42<\/figcaption><\/figure>\n\n\n\n
\"\"
I made it a private channel so not all users are bothered with the alerts \ud83d\ude42<\/figcaption><\/figure>\n\n\n\n
\"\"
Next step is to add a webhook connector.<\/figcaption><\/figure>\n\n\n\n
\"\"
Choose it from the list and klick add and configure<\/figcaption><\/figure>\n\n\n\n
\"\"
Give the webhook a name you can relate to the alert<\/figcaption><\/figure>\n\n\n\n
\"\"
Copy the url to notepad (you need it later) as the url the monitoring Powershell script will need a place to send the errors \ud83d\ude42<\/figcaption><\/figure>\n\n\n\n
\"\"
So this concludes the teams part of the solution, so lets move on to the command line stuff :-).<\/figcaption><\/figure>\n\n\n\n

Installing and configuring the script on the Raspberry Pi<\/strong><\/p>\n\n\n\n

After downloading the script I ran this Powershell oneliner to test if the script was working as expected.<\/p>\n\n\n\n

pwsh -ExecutionPolicy Bypass -file Send-vSphereAlarms.ps1 -vcenter vcenter-fqdn<\/em> -TeamsUri uri<\/em><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

<\/p>\n\n\n\n

Where vCenter fdqn is the URL for the vCenter obvious \ud83d\ude42 and the TeamsURI is the URL you copied earlier from the teams web hook configuration.<\/p>\n\n\n\n

CronJob<\/strong><\/p>\n\n\n\n

To make it possible for a Powershell script to run on a Raspberry Pi you need to install Powershell. Microsoft has good documentation regarding this subject here: Installing PowerShell on Raspberry Pi OS – PowerShell | Microsoft Docs<\/a>. I did it by running these commands in terminal on the raspberry pi.<\/p>\n\n\n\n

wget https:\/\/github.com\/PowerShell\/PowerShell\/releases\/download\/v7.2.1\/powershell-7.2.1-linux-arm32.tar.gz<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Next step is to create a folder for Powershell to be installed.<\/p>\n\n\n\n

mkdir ~\/powershell<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Then its time to unpack the downloaded tar file.<\/p>\n\n\n\n

tar -xvf .\/powershell-7.2.1-linux-arm32.tar.gz -C ~\/powershell<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Pro tip: I made my life easier by creating a symlink so I don’t need to browse to the Powershell folder to use pwsh.<\/p>\n\n\n\n

sudo ~\/powershell\/pwsh -command ‘New-Item -ItemType SymbolicLink -Path “\/usr\/bin\/pwsh” -Target “$PSHOME\/pwsh” -Force’<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

To make the script work you also need VMware PowerCLI to be installed, this can be done by running this command inside the Raspberry Pi terminal session (inside Powershell).<\/p>\n\n\n\n

Install-Module -Name VMware.PowerCLI -Scope CurrentUser<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n

After installing the PowerCLI addon you can now connect to the vCenter by running this command. For me I added this line as a first line to the Powershell script, there are probably better ways to do this and i’ll update the blog on how to do this but for now it works :-). Do not use cleartext passwords scripts in production environments!!<\/p>\n\n\n\n

Connect-VIServer -Server vcenter.ad.wrsolutions.nl -User administrator@vsphere.local -Password “thisisnotforproductionenvironments”<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

So now it’s time to test the script running from inside the Raspberry Pi. you can do this by downloading the .ps1 file to the Raspberry Pi (in my case i downloaded it to the my documents folder for the Pi user. And then running the following command in terminal from inside the Documents folder:<\/p>\n\n\n\n

pwsh .\/send-vSphereAlarms.ps1 -vcenter <vcenter name> -teamsuri <teams uri><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Where vCentername is the name of the venter and Teamsuri is the Webhook URL created earlier. in my case this gave this output<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

After that you need to create a cron job that runs the script on set times and posts the results. To do this type this command in Terminal.<\/p>\n\n\n\n

sudo crontab -e<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

If it is the first time you open crontab on your Raspberry Pi you will be asked how you want to edit the cronjobs I chose nano (option 1).<\/p>\n\n\n\n

Scroll down to the bottom and add the script, what this line does is run the Powershell script every 5 minutes.<\/p>\n\n\n\n

*\/5 * * * * pwsh -File “\/home\/pi\/Documents\/send-vSphereAlarms.ps1 -vcenter <vcenter name> -teamsuri <teams uri><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n

So after waiting for a bit I got my first error in my Teams channel <\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

So there are probably a thousand way’s to solve this, and some of them better than mine. But I went for this solution because I had the stuff laying around and I wanted to see what was possible. Hope this helps someone \ud83d\ude42<\/p>\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

Problem When you have your own (VMware) Lab you don’t always have time to look at the state of the lab and if ‘all lights are in the green’ so to say. So how cool …<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[14],"tags":[],"class_list":["post-410","post","type-post","status-publish","format-standard","hentry","category-vmware"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p59CpB-6C","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.gerjon.com\/index.php?rest_route=\/wp\/v2\/posts\/410","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.gerjon.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.gerjon.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.gerjon.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.gerjon.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=410"}],"version-history":[{"count":6,"href":"https:\/\/www.gerjon.com\/index.php?rest_route=\/wp\/v2\/posts\/410\/revisions"}],"predecessor-version":[{"id":919,"href":"https:\/\/www.gerjon.com\/index.php?rest_route=\/wp\/v2\/posts\/410\/revisions\/919"}],"wp:attachment":[{"href":"https:\/\/www.gerjon.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=410"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gerjon.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=410"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gerjon.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=410"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}