In this video, I walk through setting up the Azure Monitor solution for Windows Virtual Desktop Spring Update. The video starts by setting up a Log Analytics workspace, then adding the Session Hosts to send performance data to the Log Analytics Workspace. After that, Azure Diagnostic data is configuring to send data to Log Analytics. Lastly, the Workbook available from Microsoft is deployed to view WVD performance and session information.Continue reading “Monitoring Windows Virtual Desktop Spring Update with Log Analytics”
Microsoft has a lot of options to view Azure log data in one form or another. There is the Security Center, Azure Sentinel, Log Analytics, and Insights. This is fine for an Azure centric organization, but many organizations already have log collection systems in place such as Splunk, and using multiple logging platforms is not efficient. This article walks through sending Azure AD and Office 365 logs to Splunk.Continue reading “Use Splunk to Collect Logs from Office 365 and Azure AD”
Today I am publishing a utility called PingTimeLog. The idea is simple; ping a group of servers and write the response time to Azure Log Analytics. This utility is intended to be run as a Runbook on an Azure Automation Hybrid Worker. Alternatively, it will run as a scheduled task on a server in your datacenter. The output is written to Azure Log Analytics as a custom Type, allowing users to plot response times in a time chart.
I see a lot of potential in Azure Log Analytics. That should go without saying considering the amount of time I have spent learning and documenting it over the past few weeks. One of the most exciting features that adds tremendous flexibility is the ability to log directly to Log Analytics with the Web API. Logging to the Web API enables anything to be written to Log Analytics without the use of the Microsoft Monitoring agent. Continue reading “Azure OMS Log Analytics Step by Step – Data Collector API”
Odds are, you were Googling something like ‘write event log PowerShell’ and you stumbled on this page. If that’s the case and you just want to write an event to the Event Log to test something like a monitoring or alerting app, I won’t disappoint, below is what you need to know. If you want a little more information on writing to the Event Log as part of a script, keep going.
Write-eventlog requires 4 parameters, EventID, LogName, Message and Source. It’s the -Source part that trip people up. If you don’t know what the source is, simply make one up. Create the new source with the New-Eventlog command like this:
New-EventLog -LogName <Log you are writing to> -Source ‘Make one up’
For example, Adding the source HAL to the application log looks like this:
New-EventLog -LogName Application -Source ‘HAL’