Select to view content in your preferred language

Monitor 2023.3 database connection

1593
13
12-15-2023 01:58 PM
Pat_Gallagher
New Contributor III

I upgraded our ArcGIS Monitor to 2023.3 and now the database data is not showing correctly. There is a new Alerts section in the database and that seems to be breaking the database links to Monitor.

Pat_Gallagher_4-1702677336675.png

ArcGIS Monitor 2023.2

Pat_Gallagher_5-1702677365684.png

ArcGIS Monitor 2023.3

After the upgrade I am not getting any metric data showing in any serial chart. It looks like the database is not accepting any new information.

 

13 Replies
AYUSHYADAV
Occasional Contributor

Hi @DerekLaw ,

I can see from the ArcGIS Monitor documentation that version 2023.3.1 has been released.

AYUSHYADAV_0-1706631012108.png

But I can't find the setup for the same from my Esri. Below is the screenshot attached for the same

AYUSHYADAV_1-1706631105670.png

Can you tell me when we can expect to get it available on my Esri?

Thanks

Ayush

0 Kudos
DerekLaw
Esri Esteemed Contributor

Hi @AYUSHYADAV,

ArcGIS Monitor 2023.3.1 is scheduled to be released today. I will post an update when it's available on MyEsri. Thanks for your patience.

UPDATE: The release is now available


Hope this helps,

AYUSHYADAV
Occasional Contributor

Thanks for the update! @DerekLaw .

TimLehn
New Contributor II

I just upgraded to this version and had same issue.  In trying to resolve it I somehow lost connectivity to my database and it now would like me to register a database but when i try there are lots of errors with GUI.    

error: insert into "strategies_registry" ("description", "name", "r_id", "subtype", "type") values ($1, $2, $3, $4, $5), ($6, $7, $8, $9, $10), ($11, $12, $13, $14, $15), ($16, $17, $18, $19, $20), ($21, $22, $23, $24, $25), ($26, $27, $28, $29, $30), ($31, $32, $33, $34, $35), ($36, $37, $38, $39, $40), ($41, $42, $43, $44, $45) on conflict ("r_id") do update set "name" = excluded."name", "description" = excluded."description", "type" = excluded."type", "subtype" = excluded."subtype" - there is no unique or exclusion constraint matching the ON CONFLICT specification

0 Kudos