Use the Reporting Activity Manager

In this video, we’ll show you how to use the Reporting Activity Manager to quickly diagnose and fix reporting capacity issues during peak reporting times. First, to manage reporting activity, you must be assigned a product admin role for Customer Journey Analytics in the Adobe Admin Console. Check out CJA Access Control for more details. Once you have the appropriate permissions, open Customer Journey Analytics. You can find the Reporting Activity Manager under Tools in the top navigation. As a product administrator, you need to know how much of the reporting capacity is being used across all connections in your organization to quickly identify potential bottlenecks. Here, the Reporting Activity Manager shows you the list of all base connections enabled in your organization. For each connection, you can view the reporting activity data presented at the time the page was last loaded. The Data Views column contains all data views that use this connection. Monitoring this is important since data view configurations can add complexity to reporting requests. Capacity utilization displays the percentage of the connection’s reporting capacity that’s being used, in real time. 100% isn’t always bad. If the average wait times are low, the system is just being used efficiently. However, it can also indicate a risk of delays, especially if the number of queued requests is growing. Speaking of which, the Queued Requests column shows you the number of requests waiting to be processed. If this number is growing along with the capacity utilization nearing 100%, the system might be overloaded. You can intervene by canceling or rescheduling less critical reports. Queued Wait Time represents the average wait time before requests begin to process. Long wait times can frustrate users and indicate performance issues. Finally, the Status column helps you identify which connections are currently in use and which are idle. The active status means that reports have been run on this connection in the last two hours. The inactive status means there has been no reporting activity in the last two hours. To view the total number of report requests for all connections in your organization, expand Show More in the top right. This will show you the monthly report request graph that includes numbers for the current month and the previous month. When troubleshooting, you may want to examine an individual connection to pinpoint the root cause of the reporting activity issues and take action. Click the connection’s name, and you will land on the Connections page. Here, you can view reporting activity data for the single connection you’ve selected. The metrics you see here are presented at the time the page was loaded. Click Refresh to update the data and get the most current information. These graphs help you understand the activity happening in the connection. The utilization graph shows the usage capacity percentage over the last two hours. Here’s what it might look like in a prod environment. It helps you identify peak usage periods and trends, showing you the viewpoints where the usage capacity rate was the highest for a specific minute.

The Distinct Users graph shows the reporting activity over the last two hours. You can view the maximum number of distinct users for any specific minute to identify sudden spikes or drops that may suggest outages or access problems. Here’s what this graph might look like in a prod environment.

The Requests graph shows you how many requests were processed and how many were queued over the last two hours. You can view the maximum number of requests for a specific minute. Monitoring this data can help with detecting anomalies and load balancing. For example, this may prompt you to schedule heavy reports during off-peak hours. Here’s what this graph might look like in a prod environment.

The Queuing graph displays how many seconds on average reporting requests were waiting in the queue over the last two hours. You can see the viewpoints where the maximum average wait time was highest for any specific minute. This helps you pinpoint delays and potential performance issues. You can hide graphs as needed. The table here shows you reporting activity data for this connection presented by requests, users, projects, and applications.

The Requests tab lists all requests made in this connection. For each request, you can see its details, including the request ID, how long it has been running, its start and wait time, and so on. View our documentation for detailed descriptions of each column. The Users tab lists all users who initiated requests in this connection. It includes the number of requests the user has initiated, the number of projects associated with this user, and the average request complexity, and so on. View our documentation for detailed descriptions of each column. If the user is marked as unrecognized, it means they are in a login company where you don’t have admin permissions. The Projects tab contains all saved workspace projects where requests were initiated in this connection. For each project, it details the number of requests for this project, the number of users who made these requests, the average request complexity, and so on. View our documentation for detailed descriptions of each column. The Application tab lists all applications where requests were initiated in this connection. There are many applications the Reporting Activity Manager supports, such as Analysis Workspace UI, Workspace Scheduled Projects, Report Builder, and so on. For the detail lists, see the documentation. Now, let’s say you want to cancel specific requests to reduce the load. You would simply select them and click Cancel Requests. Similarly, you can cancel reporting requests made by one or more users, as well as cancelled requests by project and by application. The Cancellation Message field in the Cancellation dialog shows a default message your users will see when their requests are cancelled. You can always update it as needed. You can also choose to restrict future requests for a set time period. The User and Project option looks at the users who initiated the requests you’ve selected and the projects associated with these requests. Choosing this option temporarily blocks these users from running request activity for these projects. This could be useful when a user is overloading the system with a report from a specific project. The User option temporarily prevents the users who initiated selected requests from submitting any reporting requests, regardless of the project. You could choose this if, for example, a user is submitting multiple heavy requests across different projects. The Project option temporarily restricts all users from submitting reporting requests for the projects associated with the requests you’ve selected. You can do this when particular projects are causing widespread performance issues. Finally, specify how long requests will be restricted. One minute is the default, but you can also choose between 5, 10, 15, or 30 minutes. Once confirmed, you can’t lift the restrictions early. They’ll expire automatically after the duration you’ve selected. Once done, simply continue with cancellation. Once the requests are cancelled, the users trying to access an affected project and analysis workspace will see the restriction message. They will also see a similar message on the affected visualization. You should now know how the Reporting Activity Manager can help you optimize reporting performance during high demand periods. Thanks for watching!