nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Monitor 2025.1: Rows Total Metric no longer reporting for Relational Datastore

DavidColey

Hello - since I updated ArcGIS Monitor from 2025.0 to 2025.1 I am now no longer getting a Rows Total counts metric for the relational datastore.

I tried restarting the ArcGIS Datastore service on the datastore machine but still nothing.

Other than trying to restart the server itself, does anyone know of a fix?

Thanks

Find more posts tagged with

Accepted answers

DerekLaw

Hi @DavidColey,

> ... since I updated ArcGIS Monitor from 2025.0 to 2025.1 I am now no longer getting a Rows Total counts metric for the relational datastore.

This has been identified as a bug which was opened 9 days ago. Sorry for the inconvenience.

BUG-000178340 - ArcGIS Monitor Rows Total (rows) is showing 'No data available.

We are looking into this now.

Hope this helps,

All comments

DerekLaw

Hi @DavidColey,

> ... since I updated ArcGIS Monitor from 2025.0 to 2025.1 I am now no longer getting a Rows Total counts metric for the relational datastore.

This has been identified as a bug which was opened 9 days ago. Sorry for the inconvenience.

BUG-000178340 - ArcGIS Monitor Rows Total (rows) is showing 'No data available.

We are looking into this now.

Hope this helps,

MarlonAmaya

Hi @DavidColey ,

Thank you for your post. The defect provided is correct as it affects the Total Rows Metric. However it is not attributed to an upgrade and therefore would like to know about your specific scenario to truly confirm and attach your account to the defect. Please log a support case and reference the defect number.

If running into the defect, you would be able to see specific SELECT query at the inventory observer. Here are two samples I can provide. These are the two SELECT queries that we are aware of at this time.

SELECT tr.table_name AS table_name, (pg_total_relation_size(tr.schema || '.' || tr.table_name) + pg_total_relation_size(tr.schema || '.' || 'i' || tr.registration_id)) AS storage_used, st.n_live_tup AS rows_total FROM SDE_table_registry tr JOIN pg_stat_user_tables st ON tr.table_name = st.relname WHERE tr.schema .....

SELECT REPLACE(I.name, tr.database_name || '.', '') AS table_name, (pg_total_relation_size(REPLACE(I.name, tr.database_name || '.', '')) + pg_total_relation_size(tr.schema || '.' || 'i' || tr.registration_id)) AS storage_used, st.n_live_tup AS rows_total FROM SDE_table_registry tr JOIN GDB_ITEMS AS I ON tr.DATABASE_NAME || '.' || TR.OWNER || '.' || TR.TABLE_NAME = LOWER(I.PHYSICALNAME) JOIN pg_stat_user_tables st ON tr.table_name = st.relname WHERE tr.schema = 'xyz' - relation "xyz" does not exist.

Marlon

DavidColey

Hello @MarlonAmaya

"If running into the defect, you would be able to see specific SELECT query at the inventory observer."

Where do I locate the "SELECT query at the inventory observer"?

I am also reading in the SELECT statements above:

".../FROM SDE_table_registry..."

How would I have select statements involving the SDE_table_registry for a Relational Datastore? Am I missing something?

I can tell you I have the following log entry for the observer that occurred after I completed the upgrade:

{"id":8660,
"level":"warning",
"message":"Run failed",
"timestamp":"2026-01-23T21:23:00.648Z",
"code":"E_OBSERVER_FAILURE",
"process_id":null,"resource":"observers:58",
"details":"",
"trace_id":null,
"client_ip":null,
"machine":"RELDATASTORESERVER",
"username":null,
"elapsed":null,
"payload":null}

And then here is a screenshot of the graphic:

showing counter stopping at the time I completed the upgrade on 01/22/2026 at 11:00 a.m. EST

Thanks -

@DerekLaw

DavidColey

Hello @MarlonAmaya - did you have any more info for me regarding my questions to you from yesterday?

thanks

MarlonAmaya

Hi @DavidColey ,

Check the metrics observer for the Data Store component the message will be something like "Query Failed - observer data will be incomplete". If you click into view details, you will see similar to below. Here is an example:

In regards to your statement on Table_Registry. You are not missing anything, Datastore back end contains the table specified.

Marlon

DavidColey

ok thanks @MarlonAmaya . interesting re Datastore back end.... yes the error message I receive is not what you show, but what I show above as an E_OBSERVER_FAILURE code and "Run Failed" message. Probably not the same issue.

MarlonAmaya

@DavidColey - submit the support case and reference this forum link so we can confirm internally.

Thank you

DavidColey

Yes @MarlonAmaya I did that a couple days ago. Case Number is 04097357.

The support submittal does reference this thread.

DavidColey

Hello @MarlonAmaya - is there any more movement on this? My closed case has the attached bug "BUG-000178340" still shows as 'In Review'. Any more updates?

MarlonAmaya

Hi @DavidColey ,

Thank you for the follow up. Unfortunately, this is not something I would be aware of, in terms of timeline for a fix. If your account is attached to the defect, you can provide a business impact statement to gain more visibility.

https://support.esri.com/en-us/knowledge-base/provide-a-business-impact-statement-for-a-bug-000024129

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.