View reporting activity in the Reporting Activity Manager

Last update: 2023-10-31
  • Created for:
  • User
    Admin

The Reporting Activity Manager enables administrators to quickly diagnose and fix reporting capacity issues during peak reporting times.

For more information about Reporting Activity manager, including key benefits and permission requirements, see Reporting Activity Manager overview.

View reporting activity for all report suites

  1. In Adobe Analytics, go to Admin > Reporting Activity Manager.

    A list of your enabled base report suites is displayed.

    reports queue

  2. (Optional) You can search or filter the list of report suites:

    • Use the search field to search for a specific report suite. Begin typing the report suite name or ID and the list of report suites updates as you type.

    • Select the Filter icon Filter icon to expand the list of filter options. You can filter by Favorites or Status.

      To mark a report suite as a favorite, select the star icon to the left of the report suite name.

  3. View utilization information about each report suite. The data shown in the table represents the reporting activity for the report suite at the time the page was last loaded.

    The following columns are available:

    UI Element Description
    Report Suite The base report suite whose reporting activity you are monitoring.
    Virtual report suites Shows all virtual report suites that feed into this base report suite. Virtual report suites add complexity to reporting requests due to additional levels of applied filtering and segmentation. All requests that are coming from the virtual report suites are combined into the base report suite.
    Capacity utilization The percentage of the report suite’s reporting capacity that is being used, in real time.

    Note A usage capacity that is at 100% doesn’t necessarily suggest that you should immediately start cancelling reporting requests. 100% usage capacity can be healthy if the average wait time is reasonable. On the other hand, 100% usage capacity could suggest a problem if the number of queued requests is also growing.
    Queued requests The number of requests waiting to be processed.
    Queue wait time The average wait time before requests begin to process.
    Status The possible statuses are:
    • Active (blue): Reports have been run on the report suite in the last 2 hours. The data shown in the table represents the reporting capacity for the report suite at the time the page was last loaded.
    • Inactive (gray): No reports have been run on the report suite in the last 2 hours, so no data is displayed for the report suite.

View reporting activity for a single report suite

  1. In Adobe Analytics, select Admin > Reporting Activity Manager.

  2. Select the linked title of the report suite for which you want to view details.

    Reporting activity data is displayed for the report suite that you selected.

  3. (Optional) When a connection first loads in the Reporting Activity Manager, the data displayed represent the current utilization metrics. To see updated metrics after the initial load, select the Refresh button to manually refresh the page.

  4. Use the available graphs and table to understand reporting activity in the report suite.

View graphs

The following graphs are available to help you better understand the activity happening in the report suite.

If graphs are not visible, select the Show graphs button.

Utilization graph

The Utilization graph shows reporting utilization for the selected report suite over the last 2 hours.

Hover over the chart to view points in time where the usage capacity percentage was highest for that minute.

  • X-axis: The reporting usage capacity over the last 2 hours.

  • Y-axis: The reporting usage capacity percentage, by minute.

    utilization graph

Distinct Users graph

The Distinct Users graph shows the reporting activity for the selected report suite over the last 2 hours.

Hover over the chart to view points in time where the maximum number of users was highest for that minute.

  • X-axis: The reporting activity over the last 2-hour time frame.

  • Y-axis: The number of users who have made reporting requests, by minute.

    Distinct Users graph

Requests graph

The Requests graph shows the number of processed and queued requests for the selected report suite over the last 2 hours.

Hover over the chart to view points in time where the maximum number of requests was highest for that minute.

  • X-axis: The number of processed and completed requests over the last 2-hour time frame.

  • Y-axis: The number of processed requests (in green) and queued requests (in purple), by minute.

    Distinct Users graph

Queueing graph

The Queueing graph shows the average queue wait time (in seconds) for reporting requests for the selected report suite over the last 2 hours.

Hover over the chart to view points in time where the maximum average wait time was highest for that minute.

  • X-axis: The average queue wait time for reporting requests over the last a 2-hour time frame.

  • Y-axis: The average wait time (in seconds).

    Distinct Users graph

View table

When viewing the table, consider the following:

  • You can choose to view data by choosing any of the following tabs at the top of the data table: Request, User, Project, or Application.

  • You can search or filter the list of connections:

    • Use the search field to search for a specific connection. Begin typing the connection name or ID and the list of connections updates as you type.

    • Select the Filter icon Filter icon to expand the list of filter options. You can filter by Status, Complexity, Application, User, or Project.

    • You can select Hide graphs to show only the table.

table tabs

View data by request

When you select the Request tab, the following columns are available in the table:

Column Description
Request ID A unique ID that can be used for troubleshooting purposes. To copy the ID, select the request, then select the option, Copy request IDs.
Time run How long the request has been running.
Start time When the request started processing (based on the administrator’s local time).
Wait time How long the request has been waiting before being processed. This value is generally at “0” when there is enough capacity.
Application The applications supported by the Reporting Activity Manager are:
  • Analysis Workspace UI
  • Workspace scheduled projects
  • Report Builder
  • Builder UIs: Segment, Calculated Metrics, Annotations, Audiences, etc.
  • API calls from 1.4 or 2.0 API
  • Intelligent alerts
  • Share with anyone links
  • Any other application that queries the Analytics reporting engine
User The user who initiated the request.

Note: If the value of this column is Unrecognized, this means that the user is in a login company where you do not have administrative permissions.
Project Saved Workspace project names, API Report ID’s, etc. (Metadata can vary across various applications.)
Status Status indicators:
  • Running: Request is currently being processed.
  • Pending: Request is waiting to be processed.
Complexity Not all requests require the same amount of time to process. Request complexity can help provide a general idea about the time required to process the request.

Possible values include:

  • Low
  • Medium
  • High
This value is influenced by the values in the following columns:
  • Month boundaries
  • Columns
  • Segments
Month boundaries The number of months that are included in a request. More month boundaries adds to the complexity of the request.
Columns The number of metrics and breakdowns in the request. More columns adds to the complexity of the request.
Segments The number of segments applied to the request. More segments adds to the complexity of the request.

View data by user

When you select the User tab, the following columns are available in the table:

Column Description
User The user who initiated the request. If the value of this column is Unrecognized, this means that the user is in a login company where you do not have administrative permissions.
Number of requests The number of requests initiated by the user.
Number of projects The number of projects associated with the user.
Application The applications supported by the Reporting Activity Manager are:
  • Analysis Workspace UI
  • Workspace scheduled projects
  • Report Builder
  • Builder UIs: Segment, Calculated Metrics, Annotations, Audiences, etc.
  • API calls from 1.4 or 2.0 API
  • Intelligent alerts
  • Share with anyone links
  • Any other application that queries the Analytics reporting engine
Avg complexity The average complexity of requests initiated by the user.

Not all requests require the same amount of time to process. Request complexity can help provide a general idea about the time required to process the request.

The value in this column is based on a score that is determined by the values in the following columns:

  • Avg Month boundaries
  • Avg Columns
  • Avg Segments
Avg Month boundaries The average number of months that are included in the requests. More month boundaries adds to the complexity of the request.
Avg Columns The average number of metrics and breakdowns in the included requests. More columns adds to the complexity of the request.
Avg Segments The average number of segments applied to the included requests. More segments adds to the complexity of the request.

View data by project

When you select the Project tab, the following columns are available in the table:

Column Description
Project The project where the requests were initiated.
Number of requests The number of requests associated with the project.
Number of users The number of users associated with the project.
Application The applications supported by the Reporting Activity Manager are:
  • Analysis Workspace UI
  • Workspace scheduled projects
  • Report Builder
  • Builder UIs: Segment, Calculated Metrics, Annotations, Audiences, etc.
  • API calls from 1.4 or 2.0 API
  • Intelligent alerts
  • Share with anyone links
  • Any other application that queries the Analytics reporting engine
Avg complexity The average complexity of requests included in the project.

Not all requests require the same amount of time to process. Request complexity can help provide a general idea about the time required to process the request.

The value in this column is based on a score that is determined by the values in the following columns:

  • Avg Month boundaries
  • Avg Columns
  • Avg Segments
Avg Month boundaries The average number of months that are included in the requests. More month boundaries adds to the complexity of the request.
Avg Columns The average number of metrics and breakdowns in the included requests. More columns adds to the complexity of the request.
Avg Segments The average number of segments applied to the included requests. More segments adds to the complexity of the request.

View data by application

When you select the Application tab, the following columns are available in the table:

Column Description
Application The application where the requests were initiated.
Number of requests The number of requests associated with the application.
Number of users The number of users associated with the application.
Number of projects The number of projects associated with the application.
Avg complexity The average complexity of requests associated with the application.

Not all requests require the same amount of time to process. Request complexity can help provide a general idea about the time required to process the request.

The value in this column is based on a score that is determined by the values in the following columns:

The value in this column is based on a score that is determined by the values in the following columns:
  • Avg Month Boundaries
  • Avg Columns
  • Avg Segments
Avg Month boundaries The average number of months that are included in the requests. More month boundaries adds to the complexity of the request.
Avg Columns The average number of metrics and breakdowns in the included requests. More columns adds to the complexity of the request.
Avg Segments The average number of segments applied to the included requests. More segments adds to the complexity of the request.
Previous page
Next page

On this page