4 Ways To Transform Your Wave Event Monitoring Application
From Truck to Lamborghini
Wave’s Event Monitoring (EM) app provides 15 pre-built dashboards that help bridge the gap between raw event data and visualization. Like a truck, it can handle great exertions of power and haul large items, but ultimately lacks the detail and proficiency of a Lamborghini. In this blog post we focus on expanding the functionality of Wave to add greater value to your current Event Monitoring dashboards. We will provide four tips to increase productivity by utilizing alerts, creating benchmarks, normalizing data, and implementing summary views to amplify the horsepower. But before we begin, here is a brief overview of EM. Tighten your seatbelt, here we go……..
What is Event Monitoring?
With the plethora amounts of user data circling through your Salesforce organization, it is critical to monitor your org for abnormal user behavior such as unwarranted login attempts, visualforce requests, and page performance. Specifically, EM for Salesforce tracks your company’s health from a performance and user adoption perspective in terms of number of clicks to a particular Uniform Resource Identifier (URI), page load time for a visualforce page, and user login data to track where and how a user is accessing your Salesforce org. Now that we have a brief overview of EM, let’s move forward with our four tips.
#1 Setting Up Alerts
Just like a Lambo, Wave’s Event Monitoring app has built-in functionality that will notify you when something is wrong or when maintenance is required. It is like having a personal mechanic at your fingertips to call you before your automobile breaks down and wreck havoc on other parts of the engine. In Wave, alerts will notify the user when a data threshold has been reached. Users will want to take advantage of this feature so that they know when there is a hiccup in their system — for example, if a page is taking longer to load or total user clicks to reach an API endpoint is higher than average.
To set up a notification, hover over the number widget → select “Set Notification” → fill in the information to set the conditions. Review the screenshot below for reference.
To take it one step further, we also recommend implementing a Summary Dashboard (more information about this in the next section). A Summary Dashboard contains Key Performance Indicators (KPI) which are tailored to your specific needs and trigger the alerts for each number widget. Users will receive email notifications based on the conditions they have set. This provides the user with immediate access to a summary of their EM data, increases efficiency, and eliminates the need of having to visit each dashboard one-by-one. Do not worry about the emails being spam — users will only receive an email if the conditions are met.
#2 Summary Dashboard
The purpose of creating and utilizing a Summary Dashboard is to consolidate critical KPI’s from across the 15 pre-built dashboards to provide a bird’s eye view of what is occurring across your event logs. This high level approach will allow you to efficiently monitor your events and drill down and dissect the problem when needed.
The screenshot below is an example of our Sales Summary Dashboard. This can be converted to include EM data and KPI’s. What you are seeing is a summary view of each individual dashboard. You can dig deeper into each lens by clicking the link that will take you to a more detailed page of each lens for you to drill down.
The out-of-the-box dashboards reflect arithmetic functions, such as min, max, and avg. What we found extremely beneficial in our implementation with customers is having a benchmark that uses conditional highlighting to show when KPI’s are in the green or red. An example of this is taking the average number of clicks and comparing it to the overall action that occurred within the last 2 weeks, drillable by user. With this added feature you will get the extra power and insight needed to quickly identify any underlying issues.
#4 Normalizing the Data
Currently, some event log data are not normalized. You will see ID’s instead of actual strings. One way around this is to map each prefix to both standard and custom object. Secondly, depending on your needs, it may be possible to bring in external datasets from your target dataset to map to actual account names.
Let’s go for a ride!
Implementing the tips we have discussed in this blog will get you into the driver seat. You will be in command of your data, have control over your Salesforce org, and observe an increase in productivity without having to lose time deciphering data. If you found this post interesting, please share it with your network on Twitter or LinkedIn.