Use Event Monitoring Analytics to Get Insights into Your User Activity
- Use prebuilt dashboards to find answers to audit questions.
- Drill down in dashboards to explore your data.
- Set email notifications when KPIs hit specific limits.
Gain Key Insights and Take Action with Event Monitoring Analytics
As the Salesforce admin for DTC Electronics, you’ve set up Event Monitoring Analytics. It’s working the way you want, so now it’s time to get ready for your upcoming meeting with the CIO in a couple days. Let’s take your dashboards for a test drive.
- Are there report download trends we should be concerned about?
- Who has downloaded the most reports?
- Are there any reports that have performance problems?
And you know that your CIO has an inquiring mind, so try to anticipate other questions she can have and answer them before she even has to ask. You also explore some of the other cool things that the app lets you do. Along the way, you discover just how easy it is to use Event Monitoring Analytics to gather key insights and take action on them.
Spot Problems with Report Usage
Let’s use the Reports prebuilt dashboard to see the top viewed reports, spot performance problems, and identify the users who use the reports.
- Open your Analytics for CIO app, if it’s not open already.
Click the Reports dashboard.Take a look at the Report Trends by User area in the dashboard. The chart tells us the number of reports downloaded by user in the last 30 days. Hmm... looks like Bob Bandit downloaded many reports on November 17. Let’s investigate further.
Let’s look at the Reports Names by User area in the dashboard.
High Net-Worth Contacts is a popular report with a single user—whom can it be? Hover over the report name in the grid to see who accessed it. It’s Bob Bandit!Looks like Bob Bandit accessed the report a total of 150 times during November. Definitely noteworthy info to discuss with your CIO in your upcoming meeting.
See How Reports Are Performing
Now that we’ve spotted some report download trends and possible security breaches, let’s turn to a milder topic—how to spot performance problems with reports in your org. You don’t want your users to be frustrated with report performance, and you also don’t want your overall org performance to suffer with super-long queries. Let’s take a look at the Reports dashboard again.
- DB_TOTAL_TIME is the time in nanoseconds for a database round-trip.
- CPU_TIME is the CPU time in milliseconds used to complete the request. This measure indicates the amount of activity taking place in the app server layer.
Compare the DB_TOTAL_TIME to CPU_TIME to determine whether performance issues are occurring in the database layer or in your own code. In the example above, you can see that the CES Top Prospects report has a high database time as well as a high CPU time. The report might benefit from query optimization.
Set Your Performance Alarms
In the previous section, you learned how to spot report performance problems using the Reports dashboard. Perhaps you also noticed that the database and CPU time are reported as KPIs at the top of the Reports dashboard.
Cool, huh? Now that you know what DB Time and CPU Time mean, you can spot performance problems by reviewing the KPIs periodically.
But what if you don’t have time to drill into the dashboards every day? Well, there’s an easy way to get notified by email when a KPI measure goes outside a limit you set. It’s called Set Notification. (If you want other users to be notified, they must set up their own notifications.)
Let’s send an email when our maximum CPU time reaches 600 ms (shown as 0.60 in the KPI).
On the KPI, hover over Max CPU Time, click the menu arrow, and select Set
In the notification area, enter 0.60 as the threshold value, change
the operator to Is greater than, and leave the other values as is. Keep
the default notification time and day.
- Click Save.
When you created your Event Monitoring Analytics app, you manually started the dataflow to get DTC Electronics data in your app. To ensure that your app uses up-to-date DTC Electronics data, schedule the dataflow to be rerun every day.
Salesforce generates and uploads event log files in the early morning, usually at 3:00 AM in the time zone where your Salesforce instance (like NA7) is located. Schedule the dataflow for at least a couple of hours after that so the app has the latest data and the dataflow doesn’t interrupt your use of the app. We recommend running the dataflow between 8:00 and 9:00 AM to make sure that you start your day with refreshed dashboards.
Let’s schedule it to run automatically at 8:00 AM every day.
Click the gear icon in the upper right, and select Data
Select the Dataflows subtab.
- Navigate to the app Analytics for CIO.
Open the menu on the far right of the screen next to the app icon and name. Select
Schedule, and set the time to 8:00 AM, which is outside your business
work hours so the dataflow won’t interrupt business activities. Run every 24 hours, every
- Click Save.
- Salesforce Help: Schedule the Event Monitoring Analytics Daily Dataflow
- Salesforce Developer Documentation: Top 10 Ways to Run Reports Faster
- Trailhead: Event Monitoring