Skip to main content

Using Google Charts in Exchange Powershell Scripts

I've been looking at rewriting some message tracking scripts and one the things that's helpfull when you are doing message tracking is having some nice flashy visuals to help you out. Now there are some nice 3rd party packages out there like powergadgets who will separate you from your money and also the WPF framework stuff that give you some charting functionality. But if you want something that's free and will work from any workstation/server that has powershell and a Internet connection then its hard to go past Google Charts. Once you work you way around the different URL options its pretty much just a matter of creating some code to build the URL.

So to put this into something that is actually useful here's a couple of samples that first generate Rate information from the message tracking log files on Exchange 2003 using the wonder of WMI and on Exchange 2007 using the Exchange Management Shell get-messagetrackinglog cmdlet. The script itself is pretty simple it uses a hashtable to build this rate information then loops back though the hashtable to build a Google chart Url then it creates a Winform and adds a picture control setting the location property of the picture control to the URL that was built for Google charts. The cool thing is that's all you have to do because the picture control will handle all the http request stuff and download the png image and then display it to you how cool is that ! . Well I was pretty impressed anyway and you may see this technique popping up here a little more in the future.

I've put a sample of two scripts one for 2003 one for 2007 that shows a graph of the sent and received email for the last 6 hours. To use this script you need to set the hardcoded servername variable

$servername = "servername"

I've put a download of the code here the 2007 script looks like.

[System.Reflection.Assembly]::LoadWithPartialName("System.Drawing")
[System.Reflection.Assembly]::LoadWithPartialName("System.windows.forms")

$servername = "servername"


$hcHourCount = @{ }
$dtQueryDT = [DateTime]::UtcNow.AddHours(-6)
$dtQueryDTf = [DateTime]::UtcNow
Get-MessageTrackingLog -Server $servername -ResultSize Unlimited -Start $dtQueryDT -End $dtQueryDTf -EventId "Send" | ForEach-Object{
$mdate = $_.TimeStamp
if ($hcHourCount.ContainsKey($mdate.hour)){
$hcHourCount[$mdate.hour] = [int]$hcHourCount[$mdate.hour] + 1
}
else{
$hcHourCount.Add($mdate.hour,1)
}
}
Get-MessageTrackingLog -Server $servername -ResultSize Unlimited -Start $dtQueryDT -End $dtQueryDTf -EventId "Receive" | ForEach-Object{
$mdate = $_.TimeStamp
if ($hcHourCount.ContainsKey($mdate.hour)){
$hcHourCount[$mdate.hour] = [int]$hcHourCount[$mdate.hour] + 1
}
else{
$hcHourCount.Add($mdate.hour,1)
}
}


$valueBlock = ""
$TitleBlock = ""
$lval = 0

$hcHourCount.GetEnumerator() | sort name -descending | foreach-object {
if ($lval -lt $_.value){$lval = $_.value}
if ($valueBlock -eq "") {$valueBlock = $_.value.ToString()}
else {$valueBlock = $valueBlock + "," + $_.value.ToString()}
if ($TitleBlock -eq ""){$TitleBlock = $_.key.ToString() + ":00"}
else {$TitleBlock = $_.key.ToString() + ":00" + "|" + $TitleBlock}

}

$hcHourCount
$csString = "http://chart.apis.google.com/chart?cht=bhg&chs=400x250&chd=t:" + $valueBlock + "&chds=0," + ($lval+20) + "&chxt=x,y&chxr=" + "&chxr=0,0," + ($lval+20) + "&chxl=1:|" + $TitleBlock + "&chco=00ff00&chtt=Message+Volume++Last+6+Hours"
$form = new-object System.Windows.Forms.form
$form.Text = "Last 6 Hours Graph"

#add Picture box

$pbox = new-object System.Windows.Forms.PictureBox
$pbox.Location = new-object System.Drawing.Size(10,10)
$pbox.Size = new-object System.Drawing.Size(400,250)
$pbox.ImageLocation = $csString
$form.Controls.Add($pbox)
$form.Size = new-object System.Drawing.Size(500,350)

$form.topmost = $true
$form.Add_Shown({$form.Activate()})
$form.ShowDialog()
Labels:

Popular posts from this blog

The MailboxConcurrency limit and using Batching in the Microsoft Graph API

If your getting an error such as Application is over its MailboxConcurrency limit while using the Microsoft Graph API this post may help you understand why. Background   The Mailbox  concurrency limit when your using the Graph API is 4 as per https://docs.microsoft.com/en-us/graph/throttling#outlook-service-limits . This is evaluated for each app ID and mailbox combination so this means you can have different apps running under the same credentials and the poor behavior of one won't cause the other to be throttled. If you compared that to EWS you could have up to 27 concurrent connections but they are shared across all apps on a first come first served basis. Batching Batching in the Graph API is a way of combining multiple requests into a single HTTP request. Batching in the Exchange Mail API's EWS and MAPI has been around for a long time and its common, for email Apps to process large numbers of smaller items for a variety of reasons.  Batching in the Gr...
Read more

Exporting and Uploading Mailbox Items using Exchange Web Services using the new ExportItems and UploadItems operations in Exchange 2010 SP1

Two new EWS Operations ExportItems and UploadItems where introduced in Exchange 2010 SP1 that allowed you to do a number of useful things that where previously not possible using Exchange Web Services. Any object that Exchange stores is basically a collection of properties for example a message object is a collection of Message properties, Recipient properties and Attachment properties with a few meta properties that describe the underlying storage thrown in. Normally when using EWS you can access these properties in a number of a ways eg one example is using the strongly type objects such as emailmessage that presents the underlying properties in an intuitive way that's easy to use. Another way is using Extended Properties to access the underlying properties directly. However previously in EWS there was no method to access every property of a message hence there is no way to export or import an item and maintain full fidelity of every property on that item (you could export the...
Read more

EWS-FAI Module for browsing and updating Exchange Folder Associated Items from PowerShell

Folder Associated Items are hidden Items in Exchange Mailbox folders that are commonly used to hold configuration settings for various Mailbox Clients and services that use Mailboxes. Some common examples of FAI's are Categories,OWA Signatures and WorkHours there is some more detailed documentation in the https://msdn.microsoft.com/en-us/library/cc463899(v=exchg.80).aspx protocol document. In EWS these configuration items can be accessed via the UserConfiguration operation https://msdn.microsoft.com/en-us/library/office/dd899439(v=exchg.150).aspx which will give you access to either the RoamingDictionary, XMLStream or BinaryStream data properties that holds the configuration depending on what type of FAI data is being stored. I've written a number of scripts over the years that target particular FAI's (eg this one that reads the workhours  http://gsexdev.blogspot.com.au/2015/11/finding-timezone-being-used-in-mailbox.html is a good example ) but I didn't have a gene...
Read more
All sample scripts and source code is provided by for illustrative purposes only. All examples are untested in different environments and therefore, I cannot guarantee or imply reliability, serviceability, or function of these programs.

All code contained herein is provided to you "AS IS" without any warranties of any kind. The implied warranties of non-infringement, merchantability and fitness for a particular purpose are expressly disclaimed.