You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the new admin permissions model, admins should only see the analytics for the APIs they own. However, for at least one new group, they aren't able to view any analytics. The analytics pages are accessible and they load, but all the graphs report 0s for everything.
I'm pretty sure this isn't affecting all the admin groups, so it might be specific to admin accounts that belong to multiple different groups or something else more specific. Investigate the new Communicart admin group where this was seen.
The text was updated successfully, but these errors were encountered:
The culprit turned out to be related to case-sensitivy in URL path prefixes. So this was only occurring where we had setup admin permissions with a URL scope containing uppercase characters. This isn't particularly common, and didn't affect any production APIs, but for whatever reason I've typically been setting new development and staging paths for agencies with uppercase characters (for example, /DEV/new-api and /STAGING/new-api). The way the analytics database gets indexed, it lowercases everything, so our permission scoping queries just needed to be updated to lowercase the input.
With the new admin permissions model, admins should only see the analytics for the APIs they own. However, for at least one new group, they aren't able to view any analytics. The analytics pages are accessible and they load, but all the graphs report 0s for everything.
I'm pretty sure this isn't affecting all the admin groups, so it might be specific to admin accounts that belong to multiple different groups or something else more specific. Investigate the new Communicart admin group where this was seen.
The text was updated successfully, but these errors were encountered: