---
sourceDocument: Brazil ServiceNow AI Platform Capabilities
sourceDocumentLink: https://www.servicenow.com/docs/r/servicenow-platform

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Monitoring data usage

# Monitoring data usage in Hermes {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 minutes to read  
Monitor the amount of data produced to and consumed from the Hermes cluster over time. Use the Hermes Usage Dashboard to track data inflow and outflow by topic, application, and time period.

This video covers the Hermes Usage Dashboard.

Usage data is calculated by aggregating the size of all messages sent to the cluster. The size of the message is determined by the total payload present in Kafka, including key, header,
value, and overhead. If compression is enabled, the dashboard reports the compressed payload size, which includes key, header, and message.

## Key benefits {#monitoring-data-usage-hermes__section_my4_5b1_v1c}

* Monitor Hermes performance with insights into data inflow and data outflow in megabytes for a specified time period.
* Visualize data usage over time for all topics, a single topic, or multiple applications.
* Compare data usage for topics that belong to an application.
{#monitoring-data-usage-hermes__ul_cnd_vb1_v1c}  
Figure 1. Hermes Usage Dashboard

## Required roles {#monitoring-data-usage-hermes__section_o3s_121_v1c}

The hermes_admin role is required to view the Hermes Usage Dashboard.

## Accessing the Hermes Usage Dashboard {#monitoring-data-usage-hermes__section_chk_zd1_v1c}

View usage by navigating to AllHermes Messaging ServiceUsage Dashboard.

## Multi-select for Application ID filter {#monitoring-data-usage-hermes__section_ypw_53y_fjc}

The Application ID filter displays full descriptive names alongside application identifiers so you can identify and select the application without needing to know internal shorthand codes. Only applications with active metrics
collection appear in the filter.
{#monitoring-data-usage-hermes__table_nrg_w3y_fjc__entry__2}

| Application ID | Display Name |
|-|-|
| idr | Instance Data Replication |
| cnc | ITSM DEX |
| sn_streamconnect | Stream Connect |
| sn_logstoanalytics | Log Export Service |
[ ]

{#monitoring-data-usage-hermes__table_nrg_w3y_fjc}  
The Application ID filter supports selecting multiple applications simultaneously. With the multi-select option, you can do the following:

* Compare data usage across multiple applications in a single view.
* View aggregate Total MB In and MB Out across all selected applications.
* View Topic Usage Data table with a separate row per selected application.
{#monitoring-data-usage-hermes__ul_owf_cjy_fjc}For example, you can select both IDR -- Instance Data Replication and Stream Connect to view their combined and individual usage side by side.

## Use cases {#monitoring-data-usage-hermes__section_kyj_1v5_dfc}

* Monitor data usage for an application. Determine if usage has increased or decreased over time.
* View data usage for a specific topic. Determine if usage patterns changed by looking for spikes or drops in usage.
* Compare data usage for topics in a single application or all applications that belong to you.
* Analyze total bytes in and bytes out based on the source.

  Instance
  :   Total bytes sent to and consumed from a topic by the instance. For example, select Instance to view log volume produced to a topic by Log Export Service.

  Customer
  :   Total bytes sent to and consumed from a topic by an external customer application. For example, select Customer to view log volume consumed from a topic by an external application.

  Other
  :   Total bytes sent to and consumed from a topic by an internal ServiceNow application.

  All
  :   Aggregation of all Consumer, Instance, and Other values.
{#monitoring-data-usage-hermes__ul_nyy_cv5_dfc}

## Reports {#monitoring-data-usage-hermes__section_svm_tv5_dfc}

Data displayed in the Hermes Metrics Dashboard is collected from the Hermes usage metrics \[hermes_usage_metrics\] table.

* Metric data is captured hourly, with each collection point reflecting the latest value recorded within that hour.
* Metric data is aggregated and displayed over time. This means the dashboard enables you to view an overall trend rather than precise moment-to-moment traffic.
* Metric data displayed on the dashboard is initially aggregated daily. The dashboard automatically determines the best aggregation based on the date range selected:
  * Previous months: Data is displayed using monthly aggregates, giving you a clean summary of usage for each completed month.
  * Current month: Data is displayed using daily aggregates, so you can see up-to-date usage as it accumulates throughout the month.
  * Today: When your end date is today, hourly data is included, giving you the most current view of usage activity.
  {#monitoring-data-usage-hermes__ul_zd5_gjy_fjc}
* Metric data is retained for 12 months.If your selected date range spans both past and current months,
  the dashboard combines monthly summaries for the historical portion with daily and hourly data for the current period. For example, querying January 1 -- April 9 (today is April 9).

  {#monitoring-data-usage-hermes__table_zqw_jjy_fjc__entry__2}

  | Period | Aggregation |
  |-|-|
  | January | Monthly |
  | February | Monthly |
  | March | Monthly |
  | April 1 -- April 8 | Daily |
  | April 9 (today) | Hourly |
  [ ]

  {#monitoring-data-usage-hermes__table_zqw_jjy_fjc}

  The line graph has also been updated to display monthly trends when viewing extended date ranges, making it easier to identify long-term usage patterns.
{#monitoring-data-usage-hermes__ul_z4k_b2s_w1c}  
{#monitoring-data-usage-hermes__table_kgg_fh1_v1c__entry__4}

| Title | Type | Source table | Description |
|-|-|-|-|
| Total Megabytes In | Single score | Hermes usage metrics \[hermes_usage_metrics\] table | View the aggregated total of data produced to Hermes in megabytes. |
| Total Megabytes Out | Single score | Hermes usage metrics \[hermes_usage_metrics\] table | View the aggregated total of data consumed from Hermes in megabytes. |
| Usage trends | Trend | Hermes usage metrics \[hermes_usage_metrics\] table | Monitor data usage in terms of bytes in and bytes out for selected topics over time. |
| Topic Usage Data | Table | Hermes usage metrics \[hermes_usage_metrics\] table | Monitor data usage (bytes in and bytes out) for all topics or specific topics. |
[Table 1. Dashboard reports]

{#monitoring-data-usage-hermes__table_kgg_fh1_v1c}

## Topic usage data {#monitoring-data-usage-hermes__section_bbl_fpx_2hc}

View data usage (bytes in and bytes out) by source based on the combination of application ID, service ID, and topic that you select.

The Topic Usage Data table displays only topics associated with a recognized application. Topics that were created without an Application ID no longer appear in the table or in the Hermes Topic filter.  
The following are the available options in the Hermes Topic filter:

* All - Summary --- Displays one aggregated total row per selected application. Use this for a quick snapshot of overall usage.
* All - Detailed --- Displays individual rows per topic. Use this to identify which specific topics are driving the most data usage. The sum of all rows in All - Detailed equals the All - Summary total.
{#monitoring-data-usage-hermes__ul_ukz_nyy_fjc}
{#monitoring-data-usage-hermes__table_fzh_zjy_fjc__entry__4}

| Application ID | Hermes Topic Option | What you see | How you might use it |
|-|-|-|-|
| All | All - Summary | One aggregate row per selected application. | Quickly compare total data usage across applications. |
| All | All - Detailed | Individual topic rows for all applications, excluding aggregate entries. | Identify which specific topics are driving the most usage across your organization. |
| Single App | All - Summary | One aggregate row for that application. | Get a total usage snapshot for a specific application. |
| Single App | All - Detailed | One row per individual topic for that application. | Drill into topic-level usage for a specific application. |
| Multiple Apps | All - Summary | One aggregate row per each selected application. | Compare total usage side by side across selected applications. |
| Multiple Apps | All - Detailed | One row per topic for each selected application. | Analyze topic-level breakdown across multiple applications simultaneously. |
| Any | Specific Topic | One row for that topic. | Focus on usage patterns for a single topic. |
[Table 2. Topic usage data combinations]

{#monitoring-data-usage-hermes__table_fzh_zjy_fjc}
**Related concepts**   

* [Managing Hermes settings](https://www.servicenow.com/docs/l7d9XridCjY8fm4hmzoRhw "View, modify, and manage configuration properties that control the behavior of Hermes Messaging Service. You can update property values, manage background job states, or adjust settings where automated detection is unavailable.")
* [Tracking message usage in Hermes](https://www.servicenow.com/docs/mv9Cqu6mD~J~9k6qn~ORqw "Message usage through the Hermes Messaging Service is tracked for monitoring and management purposes through the Kafka topic name.")
* [Cloning with Hermes Messaging Service enabled](https://www.servicenow.com/docs/LV9c6s0JNUi4fm2phvz2ag "To clone your database from one instance to another successfully with Hermes enabled, you must ensure that certain Hermes tables are preserved and excluded. The list of tables in the preserve list should match those in the exclude list and vice versa.")  
**Related tasks**   

* [Check the status of and connection to the Hermes Kafka cluster](https://www.servicenow.com/docs/c_jee1tuemDR5bCkb4YFTQ "Check the status of and test the connection to the Hermes Kafka cluster by sending and receiving test messages.")
* [View Hermes Messaging Service log messages](https://www.servicenow.com/docs/O0dmUQPPvovszKqvInGaEA "Review Hermes event details by viewing log messages.")

*[\>]: and then


