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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Monitoring data usage

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

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Monitoring data usage in Hermes

Hermes provides a Usage Dashboard to monitor the volume of data produced to and consumed from the Hermes cluster over time.
Data usage is calculated by aggregating the size of all messages in Kafka, including key, header, value, and overhead.
If compression is enabled, the dashboard reports the compressed payload size.
This dashboard helps ServiceNow customers gain insights into Hermes cluster performance by tracking data inflow and outflow for specified time periods.
Show full answer Show less  

## Key Features

* **Visualize data usage trends:** View data usage over time for all topics, single topics, or grouped by application, with data shown in megabytes.
* **Compare data usage:** Analyze data usage by topic, application, or source such as internal ServiceNow applications, external customer applications, or instances like Log Export Service.
* **Dynamic data aggregation:** Usage metrics are collected hourly and aggregated daily or monthly depending on the selected date range, with data retained for up to 12 months.
* **Detailed usage tables:** Monitor bytes in and out by application ID, service ID, and topic, differentiating between internal (ServiceNow-only) and external topics.
* **Role-based access:** Access requires the hermesadmin role.

## Practical Use Cases

* Track application data usage trends to identify increases, decreases, or unusual spikes and drops.
* Identify if an application is producing unsupported or declining data volumes.
* Compare data usage across multiple topics and applications to optimize message flow and resource allocation.
* Analyze data consumption patterns by internal ServiceNow processes versus external customer applications.
* Use usage data to troubleshoot performance and capacity planning for Hermes messaging clusters.

## Accessing and Data Sources

Access the Hermes Usage Dashboard by navigating to **All \> Hermes Messaging Service \> Usage Dashboard** . The dashboard sources its data from the **hermesusagemetrics** table, capturing hourly aggregated metrics that reflect the latest hourly values and provide a high-level trend rather than real-time traffic.

## Key Metrics Available

* **Total Megabytes In:** Aggregated data produced to Hermes.
* **Total Megabytes Out:** Aggregated data consumed from Hermes.
* **Usage Trends:** Bytes in and out over time for selected topics.
* **Topic Usage Data Table:** Bytes in and out by topic, filtered by application and source (internal or external).  
Monitor data usage in Hermes over time.

Monitor the amount of data that is produced to and consumed from the Hermes cluster over time in 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 or a single topic.
* 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 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.

## 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.
* Look for decreased usage over time to determine if your application is producing data that isn't supported by Hermes.
* 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. Depending on the date range you select, the dashboard dynamically adjusts its view. For example, for ranges greater than 60 days, it presents the data in monthly summaries. For ranges less than 60 days, it displays daily summaries.
* Metric data is retained for 12 months.
{#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. |
[ ]

{#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.

Topics with the prefix \[Internal\] are for applications used only by ServiceNow. Topics that don't have this prefix are considered external.
{#monitoring-data-usage-hermes__table_t3v_1k1_nhc__entry__4}

| Application ID | Hermes Topic Option | What You See | How You Might Use It |
|-|-|-|-|
| All | All | Two roll-up rows: one for external topics (\*All Topics\*), one for internal topics ("\[Internal\]\*All Topics\*"). | Quickly compare total data usage for external integrations and internal ServiceNow workflows organization-wide. |
| All | INSTANCE_ALL_TOPICS | Roll-up plus individual topic rows for all topics (external + internal) across the organization. | Identify which specific topics are driving the most data usage while still seeing the aggregate totals. |
| All | \*All Topics\* | External topics roll-up per application (topics without \[Internal\] prefix), grouped by app. | Compare external integration usage across different applications (for example, Stream Connect, Log Export Service). |
| All | \[Internal\]All Topics | Internal topics roll-up per application (topics with \[Internal\] prefix), grouped by app. | Monitor internal ServiceNow data flows across applications (for example, IDR internal topics). |
| Specific App | Any topic option | Usage for topics related to that application, based on the topic filter selected. | Focus on data usage for a particular application (for example, view Log Export Service topic usage). |
[Table 1. Topic usage data combinations]

{#monitoring-data-usage-hermes__table_t3v_1k1_nhc}  
Note:  
When All is selected for both the Application ID and Hermes Topic, the Topic Usage Data table displays two roll-up rows: one for external topics (\*All Topics\*) and one for internal topics (\[Internal\]\*All Topics\*).
**Related concepts**   

* [Managing Hermes settings](https://www.servicenow.com/docs/4wXSB4sgbI130WUd4_Ubfg "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/dsC9YNNpiRaYHiYmiqP~sw "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/qrW4yQPzi28_fP5yvWVGAA "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/vaZke1_5iy8PwnuXiFK9Dw "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/h231_9UHjWG~FnSlrCX26g "Review Hermes event details by viewing log messages.")

*[\>]: and then