Current activity
The Current activity tab of the Stats page shows the processing activity in your Sitecore Content Hub solution.
The information is divided into two sections:
-
Queue - a list of the processing queues, with numbers representing how many messages are at each stage of the queueing process.
-
Jobs - a collection of statistics about jobs, grouped by job type.
You can access the details of the jobs you created from your personal Background processes page.
For each job, one or more messages are sent to the queue, instructing queue workers to process them. Messages contain the data needed by the workers assigned to each queue to fulfill the job assignment.
A message can be in one of the following stages:
-
In - new message is created.
-
WIP (work in progress) - message is being processed.
-
Complete - message has been successfully completed.
-
Dead - message cannot be processed.
You can set up job prioritization. For example, processing image files can have a higher priority than video files so they are processed first.
Queues
The following table describes the various queues used throughout Content Hub. Some of these queues are scalable, meaning their capacity can be adjusted to accommodate infrastructure of different sizes.
Queue |
Activity |
Scalable |
---|---|---|
actions |
Handles actions invoked either through triggers or manually through the API. |
Yes |
assetlifecyle |
Optimizes storage for files located in the Azure Blob storage of an asset, whether it is archived or not. |
No |
audit |
Logs and saves activities in an Elasticsearch audit log index. |
No |
businesslogic |
Runs configurable logic when certain system events occur. Mainly used with projects and jobs. |
No |
checkout |
Moves assets to OneDrive. |
No |
chili_validation |
Validates the uploaded publication templates. Can be used for Chili integration. |
No |
cleanup |
Deletes entities that are no longer required. If an entity is linked to files, the files are also deleted. |
No |
compositeassets |
Handles entity save operations for assets based on file archives such as ZIP files. It extracts each file from the archive and associates them with the asset. |
No |
connectorpublishing |
Publishes data from connectors. |
No |
discussionnotification |
Notifies users when they are mentioned in discussions or comments. |
No |
download_reporting_logs |
Creates a download package when the user requests the download of reporting logs. |
No |
download_script_telemetry |
Creates a download package when the user requests the download of script telemetry logs. |
No |
drmcomplexity |
Forces assets to require explicit approval by updating the |
No |
duplicatefile |
Checks for duplicate files, creates fileDuplicate entities for each duplicate type, and flags duplicate assets with the property |
No |
entitypublishing |
Publishes entities to Edge. |
No |
entitypublishing_post_processing |
Processes message notifications received from Edge after publication. |
No |
exportdata |
Processes data exports. Used for exporting both Excel and translations. |
No |
fetch |
Lets users upload assets from either a UNC path or a public URL. The newly uploaded assets are then added as file entities to an existing asset entity. |
Yes |
flow |
Forwards incoming messages to a flow queue that corresponds with the message channel. Only one instance of this worker is permitted. |
No |
graph |
Provides a gateway for the graph server, which connects normalized data in the Redis data storage and de-normalized data in the Elasticsearch data storage |
No |
high_priority_fetch |
Similar to the fetch queue, except that it processes high-priority jobs. |
Yes |
high_priority_import_data |
Similar to the importdata queue, except that it processes high-priority jobs. |
No |
importdata |
Processes data imports. It is used to import Excel files, mass edits, and translations. |
No |
massedit |
Handles multiple edits on entities. It can be configured to only edit part of the entities relations and properties. |
No |
ordering |
Prepares download orders by converting and archiving files, as requested by users. |
No |
package |
Handles requests for exporting and importing packages. |
No |
processing |
Handles processing jobs based on priority. |
Yes |
publiccollection |
Makes a collection public, making all the assets in the collection available through an external website. Access to this external website can be configured to require authentication. |
No |
publiclink |
Updates the state of the public link entities in an Azure table. |
Yes |
publisher |
Every message goes through this queue before being propagated. |
No |
renditions |
Based on a specific configuration, it scans a queue of saved entities, detects property changes, and creates a processing job. |
No |
roles |
Updates the user group policies when creating, updating, or deleting a role template. |
No |
scriptcompilation |
Builds requested scripts in C#. |
Yes |
sendemail |
Sends email messages. |
Yes |
sitecore_machine_learning |
Sends information about assets to the Sitecore AI, which processes similarity metrics for specific assets. |
No |
system |
Handles large, time-consuming system jobs that are executed after an upgrade. These jobs are excluded from the upgrade process itself, but begin when the system is live. Examples of these jobs include updates to translations, themes, and large entities. |
No |
tasknotification |
Sends email notifications to users during the following situations:
|
No |
tasks |
Copies a task and assigns it to specifics users. |
No |
theme |
Generates themes based on data in a theme entity. |
No |
themenotification |
Notifies media delivery when it has to refresh the cached theme. |
No |
totalfilesize |
Sets the properties |
No |
triggers |
Whenever there are changes in the system, it checks if the trigger conditions are met and, if so, it activates the trigger. |
Yes |
upload |
Adds a new Add links button to the Create page, letting users create assets based on files from an external source. |
Yes |