Cool Azure Log Analytics: How many unique users were affected by 404’s?

Here’s another nifty little trick useful for counting how many unique users were impacted from a service issue.

In order to do this, I use the “dcount” aggregation. It counts how many unique values are in the column.

requests
| where timestamp > ago(7d)
| where resultCode == "404"
| summarize dcount(user_Id)

One thought on “Cool Azure Log Analytics: How many unique users were affected by 404’s?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s