Alert Previous Fan Failure
Karriem Drewery
Hi,
I need to monitor "host failure events" per hour over last 24 hours for a group of 50 hosts. When the total reaches a threshold like 10 fails, an alert email needs to be sent. This count and total needs to occur each hour.
What I want to do is schedule a report to count the fails by each host per hour, save the count, and then add the next hourly count to the previous count. When any host reaches 10 fails within the 24 hour window, the triggered action needs to send an email.
I created a lookup called "Failed_Count" with a file.csv that contains 2 fields host,count.
I can run a query like this>>
index=foo "failed" stats count by host outputlookup Failed_Count
and it updates, but I have no luck adding the previous hour count to the total...
We've run some maintenance scripts as well as I've relinked the entire table as I have noticed that in 3.2 the New Database Connection has changed it's look a little from 2.9.
I'm notcing this is happening with several different tools, not just one. Such as creating a new feature, reshapping, etc. So I'm not thinking it's directly related to Editing of the Versioned Geodatabase on SDE.
Any suggestions that I or the database side GIS guys can look at to try and resolve this issue?
I'm assuming it's from 3.2, but not 100% sure as I haven't worked in this database for a little over 2 weeks, but I did notice it after updating to 3.2 at least...
Thanks
The purpose of this feature is to bring up any issue that Pro internally runs into while drawing layers in the current map extent. Prior to 3.2, these alerts (warnings or errors) were getting ignored and never made the users be aware of these.
Same in my case, the geometry completely disappears after the error. Although these drawing errors being displayed are supposed to be a feature of 3.2, I find it fishy that this specific error is happening to others all while nothing appears to be wrong with our databases according to ESRIs own diagnostic tools (diagnose version metadata and diagnose version tables). ArcGIS Pro 3.2 introduced discarding and undoing edits on non-versioned data which makes me wonder if there was a bug introduced. Currently, this issue isn't documented as a bug, and when we opened up a support ticket, support seems hesitant to do so because they can't recreate the issue. Altogether, I think either there is truly something wrong with our databases that the diagnostic tools currently don't catch and we have been fortunate enough to not to receive this error in every previous version of ArcGIS Pro or there is some issue with ArcGIS pro 3.2, which seems more likely to me. As of now, I will probably just revert back to ArcGIS pro 3.1.
I was having this same issue using 3.2 with the drawing errors and the geometry disappearing. Everything would be normal until I started editing and split a line feature but discarded the edit. At that point I would start seeing the notices and the geometry would stop drawing.
I discovered that there is a new option introduced in 3.2 to "Enable and disable editing from the Edit tab" in either a single or multiple (the default) workspace edit session. If I set this to single, hit the Edit button, and select my editing workspace, as soon as I panned and zoomed around I would start seeing the drawing alerts even though everything was still drawing and I had not made any edits yet. These alerts would continuously open and close as I panned around, but the geometry for all of my layers continued to draw. Even if I split a feature and hit the Discard button the geometry did not disappear as it did before. As soon as uncheck the Edit button the drawing errors would stop. However, if I set the editing option to "Multiple workspace edit session", then split and discard the edit, the geometry would again disappear and the notifications would begin to pop up again.
Based on feedback on Drawing Error newly introduced issues in this forum is that this issue started happen in a newer version ArcGIS Pro 3.2 that was not present in previous releases, and it necessitates a workaround, it can indeed be classified as a bug. Users can workaround it , but if we need supports hundreds of users, then this will be raised as lots of supports. Result of this issues is to rollback to ArcGIS Pro 3.1 at this moment
Thanks for this work around. It keeps our geometry from disappearing during an edit session. Reminds me of how we used to start an Edit session in ArcMap. Kind of annoying that we have to do this work around just to keep our data on the screen during an edit session. One of the things that I liked about Pro vs ArcMap was not having to start an edit session and being able to edit from multiple workspaces at once. 3.2 went backwards with this bug.
Thanks for opening a support ticket. I hope they will provide you a resolution soon. The goal of this new Drawing Alerts capability is to surface up any warning/error that a layer throws while drawing. In previous releases, that was getting eaten away -- we never made the user be aware of that. Now Pro does bubble it up if something goes wrong.
Imagine we didn't have this Drawing Alerts option in 3.2, and due to upgrade or version incompatibility etc., geometries were not drawing... and imagine you have a lot of layers and features drawn in your map... it was very likely 'missing geometries' might have gone unnoticed. Now with this Drawing Alerts, Pro tells you that there were some issues it ran into while drawing those layers/features.
I have done this kind of editing through the earliest versions of Arc Pro 2 (roughly in 2018 or 19), and earlier in Arc Map 10.5 and 10.7, with very few errors in the editing process, drawing or otherwise. This is buggy behavior and not brought about by "corruption in the database", so let's hope it gets looked at as such.
This is extremely exciting news! Sadly I will not be able to update my ArcPro due to other dependencies within my organization. However, I am wondering if those who have updated to 3.3.1 can report if it has truly fixed this vexing issue?
What is the version of the geodatabase and RDBMS flavor / version being used?
Have you updated the Enterprise Geodatabase to Pro 3.2?
You could also run these 2 tools to see if there is any reported errors:
Thanks George, I had the GIS database admin to try those tools and they came back with nothing. I then decided to try to reconcile my current version and post it to SDE and this seemed to have worked. I'm no longer getting that issue currently after testing it for some time.
So that may have just been the issue with updating to 3.2 and it having a conflict with the current version I was editing of the data.
I'll respond if the error does come back, but so far so good.
I don't have the versions of the RDBMS or Geodatabase, but the Admin was going to post that for you here, but he had ESRI login issues...
Update: The issue happened once again after doing the fix yesterday. Instead of Reconciling and Posting it, I just Reconciled the version and it worked. So it somehow has to do with a versioned geodatabase on SDE. Not sure if it's directly related to ArcGIS Pro 3.2 or if it's just a random new issue not related to the new update, but I hadn't seen this error before 3.2...
Getting the version of the geodatabase and RDBMS would be most helpful for any potential troubleshooting.
Have your admin query the SDE_version table and return the info for the geodatabase side.
Ok, my hunch may have been correct....... you need to update the version of SQL Server to at least SQL 2016 to be on a supported version of SQL Server ( -requirements/latest/windows/database-requirements-sqlserver....). I would recommend something newer like 2019 or 2022 for the SQL version to get more mileage. I do not think that version of SQL Server has been supported since before Enterprise 10.9.1 / Pro 2.9 in terms of our clients and DBMS combinations.
The database admins are going to discuss upgrading, but have to check out a few things first. I think they one thing was moving over to PostGres from SQL, so maybe that was why it hasn't been updated. They also want to check about any other issues it could impact if they do update it and such.
Anyways I passed on the information. Thanks for your help and will let you know if that is in fact the solution if it does get updated to a newer version...
A few days ago, I was working on a file (some computer code) on my laptop at home which is synced to my Dropbox. I then opened the same file later on my office computer which is also synced with my Dropbox, but it did not contain the latest changes. This had me very concerned. This particular time I happened to notice the change and have "manually" updated the file, but theoretically Dropbox should have synced and opened the latest version. I am worried such a mistake may have been made previously and also might happen again. I am already rather OCD when it comes to checking the sync status and each time I begin work on a different device always ensure the Dropbox icon in the right bottom corner of my Windows taskbar is fully white indicating syncing is up to date. Similarly, I do the same each time I have finished work on a given device.
I guess there is the possibility that I may be responsible for this somehow by accident, but after reading other forum comments it does seem a real possibility that on occasion Dropbox will fail to sync and that one might open a file which has been updated on a different machine but does not contain the updates. Given that such events, which may be rare, can happen due to unforseen issues (e.g. network connection etc.), I wonder if there is anything that can be done to alert the user e.g. a pop up alert indicating that there is no Internet connection, or Dropbox hasn't yet fully synced, or similar? In addition, I wondered if anybody can share any tips / best practices for file management to safe guard against these kinds of events?
Thank you.