Latest Contributions by MegHoole

We recently learned that Esri introduced rate-limiting for AGO in September 2020.   As i understand it, rate-limiting is a new development in AGO.  It subsequently has impacted a few of our high traffic critical applications in undesirable ways including slow performance and 429 errors invoked when demand is high.  We have always operated on (what has become) the standard feature data store since 2014 without issue until summer 2021 with our wildfire application and data layers (2021 was/is a particularly active fire season for us). We find ourselves in a situation where just a handful of our AGO applications and maybe a dozen associated hosted feature layers require the performance of the high cost M4 tier that allows for higher traffic and mitigates the 429 errors we were seeing. We're hopeful that as Esri tunes the rate-limiting and premium tiers that more flexible options become available.  Possible options: cost relative to actual usage instead of a flat monthly fee for Premium Tiers enable AGO org to specify content that needs Premium Tier performance and enable AGO org to specify date ranges for when Premium Tier usage is required better documentation and transparency regarding rate-limiting and performance needs. I'd love to hear from other AGO Organizations who may have similar concerns - what works for you with the new rate-limiting and premium feature data stores and what doesn't?  Have you opted for a Premium Tier feature datastore?  Some info is available here (search page for Premium Feature Data Store as there is no direct link to the section):  https://doc.arcgis.com/en/arcgis-online/reference/faq.htm      ... View more

Currently in AGO, we must navigate to an item's settings page to update the status of an item to authoritative, deprecated or no status. Please enhance the content page so that we can select and mark multiple items as authoritative/deprecated/or no status from content page. ... View more

Add a filter to the members page that allow admin to filter for disabled accounts. This would facilitate easier member management. ... View more

Currently the AGO status report for members includes a field for last login date.   The date/time fields in the report are unfortunately configured in a manner that prevents any useful sorting.  Please fix so that the date/time fields can be sorted from earliest to latest or visa versa. We are a large organization and need to be able to determine which accounts in the report have been inactive.   The AGO members page sorts properly - the reports should also sort in the same manner. ... View more

The web map item details page lists and provides a link to all of the layers' details page or description used in the web map.  The link to the layers' item details page is useful, however, I have to open every link to determine if the layer is hosted in AGO or otherwise. From an admin perspective it would be useful and a timesaver for troubleshooting to have visual cues that indicate: the type of the layer used in the web map (i.e. hosted layer, hosted view layer, wms, rest endpoint...) is the layer editable the access (sharing) the owner visibility on/off in web map ...other ... View more

The new option to show a "notification" banner is great.  Its somewhat buried in the the Org/Settings/Security area.  It would be handier for Admins if there was an edit button shown to admins in the banner  itself.  This would allow faster enabling/disabling and editing. ... View more