O endpoint History<\/A> da REST API é uma ótima ferramenta para investigar informações sobre eventos que ocorrem em sua organização. Embora você possa facilmente baixar um CSV abrangente de eventos como administrador no ArcGIS Online, a REST API oferece a opção de personalizar os dados retornados e fazer perguntas mais específicas. Para um exemplo de como usar o CSV do history, confira este blog: https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-\/administration\/exploring-the-organization-activity-log-csv<\/SPAN><\/A> <\/SPAN><\/P> <\/SPAN><\/P>Para este blog, vou explorar as consultas necessárias para exportar informações sobre eventos de login para uma organização específica. Para usar parâmetros específicos com esta API atualmente, o formato csv deve ser usado devido a: BUG-000120745. Isso está planejado para ser resolvido em uma versão futura, mas o CSV é um ótimo formato para grandes quantidades de informação.<\/P> <\/SPAN><\/P>Cenário:<\/STRONG> Andy, o Administrador, quer entender quais de seus usuários fizeram login no ArcGIS Online e de quais aplicativos em fevereiro de 2019. Ele tem a suspeita de que seu funcionário Oreo J. Sampson não sabe sua senha, mas tem medo de pedir para redefini-la pois ele pede todos os dias. Andy vai verificar as informações de login da sua organização para confirmar<\/SPAN><\/P><\/P>Passos do Detetive:<\/STRONG><\/SPAN><\/P> <\/SPAN>Formular a consulta:<\/LI><\/OL>Url:<\/STRONG> https:\/\/sampson23.maps.arcgis.com\/sharing\/rest\/portals\/self\/history<\/A>?<\/P>Parâmetros:<\/STRONG><\/P>all=true<\/EM> 93 retorna eventos para todos os membros da organização<\/P>start=0<\/EM> 93 começa no primeiro registro<\/P>num=10000<\/EM> 93 maior quantidade de eventos retornados (requer formato csv)<\/P>f=csv<\/EM> 93 retorna resultado em csv<\/P>sortOrder=asc<\/EM> 93 saída das informações em ordem ascendente<\/P>token = 926hVsODGfBpk5X_hGc0MOrnxmddIk4bL4hP8FyOAxM0QxL3VEw86iTdB9d<\/EM> 93 token de administrador necessário<\/P>fromDate =2019-02-01<\/EM> 93 início do intervalo de datas<\/P>toDate=2019-02-28<\/EM> 93 fim do intervalo de datas<\/P>actions= failedlogin<\/EM> 93 eventos a serem retornados<\/P> <\/P>Url Exemplo construído:<\/STRONG><\/P>https:\/\/sampson23.maps.arcgis.com\/sharing\/rest\/portals\/self\/history?all=true&start=0&actions=failedLogin&sortOrder=asc&toDate=2019-02-28&fromDate=2019-02-01&num=10000&f=csv&token=<token<\/><\/><\/><\/><\/><\/><\/><\/><\/><\/><\/><\/><\/><\/><\/><\/><\/><\/><\/><\/>" rel='nofollow noopener noreferrer'>https://sampson23.maps.arcgis.com/sharing/rest/portals/self/history?all=true&start=0&actions=failedLogin&sortOrder=asc&toDate=2019-02-28&fromDate=2019-02-01&num=10000&f=csv&token=>
Parâmetros:<\/STRONG><\/P>all=true<\/EM> 93 retorna eventos para todos os membros da organização<\/P>start=0<\/EM> 93 começa no primeiro registro<\/P>num=10000<\/EM> 93 maior quantidade de eventos retornados (requer formato csv)<\/P>f=csv<\/EM> 93 retorna resultado em csv<\/P>sortOrder=asc<\/EM> 93 saída das informações em ordem ascendente<\/P>token = 926hVsODGfBpk5X_hGc0MOrnxmddIk4bL4hP8FyOAxM0QxL3VEw86iTdB9d<\/EM> 93 token de administrador necessário<\/P>fromDate =2019-02-01<\/EM> 93 início do intervalo de datas<\/P>toDate=2019-02-28<\/EM> 93 fim do intervalo de datas<\/P>actions= failedlogin<\/EM> 93 eventos a serem retornados<\/P> <\/P>Url Exemplo construído:<\/STRONG><\/P>
This is incredibly helpful information, Thanks for the great post!
I am wondering if it is possible to create this same type of log file using the python API and pandas data frame? My management is looking for statistics on user adoption and they want to see the when and how our users are accessing our AGOL site. Ideally, they would love to see stats going back to late 2017 / 2018. From what I can tell the Python API has a history method that could be used; however, I am not able to find a way to filter out unwanted events (i.e. actions=login and a subset of GIS technicians ). Also given the csv limitation (max of 10k events) and the amount of time I need to go back both AGOL Download Activity Log and the Python API history method don’t seem to be great options.
Any suggestions would be greatly appreciated.
kgerrow@esri.com
Thanks for the informative post!
I have a similar question to Matt's above -- we're trying to get a sense of how many active ArcGIS Pro users we have in a given year. Since we used named accounts, I did a query using the REST API with "actions=login" and "clientId=arcgisprodesktop" as part of the parameters. Worked well, but I'm getting hampered by the 10k limitation. Is there any way to download/access more than 10k rows at a time?
Hi,
Matt Martin/USA Martin, I'm looking into your questions with the Python API. Will let you know when I have more information.
Reina Murray, there is a 10k limit to the amount of records that can be retrieved in a single request. I would recommend either using a filter like search only for login actions to try to limit the query, or make multiple requests to the history api on different dates. This way you can break up your requests so they don't exceed the 10K limit.
The limit ensures that data queried through this API is performant, so therefor will need logic to parse through different days if you do want to collect and analyze these actions.
Reina Murray My workaround to the 10k max, though not ideal, was to use postman and make multiple requests to the history api as suggested above. However, in doing so I discovered that the history api seemed to ignore my toDate (end of date range) parameter. This meant I ended up getting duplicate events when I combined all of the csv exports together. I used the “ReqID” field as the unique identifier to remove all duplicates except the first occurrence. This can be easily done in excel using a free add-in called Kutools.
Kelly Gerrow Thank you for looking into this some more for me. I would also like to ask if you know if the history api has a limit to how far it can go back. I tried using the multiple request workflow like you mentioned above using the first and last day of each month (exp. 2018-01-01 to 2018-01-31).
My hope was to start at Jan 1st 2018 and go month by month till I reached the current date (Jan 9th 2020). The weird thing was that it was not until August (2018-08-01 to 2018-08-31) that I got my first login result of Dec 6, 2018.
I know I should have had login events prior to this date as I am able to view older content creation, deletion, and sharing events using the download activity log, located on the AGOL organization overview page. Any additional resources you may know of would be incredibility helpful.
Thank you again!!!
I tried with my ArcGIS Enterprise 10.7.1, but always the csv has not rows. There is something to do at DataStore or setting some options somewhere?
I just read the note: Only available with ArcGIS Online, then I wonder if this functionality will be migrate toward on-premise environment, I means ArcGIS Enterprise ?
Is there a way to view login events on ArcGIS Enterprise?
Hi everyone,
Any update related to login events on ArcGIS Enterprise. I got the same as @FranciscoHernandez2 when I execute the following endpoint:
https://<root>/portal/sharing/rest/portals/self/history?all=true&start=0&actions=failedLogin&sortOrder=asc&toDate=2019-02-28&fromDate=2019-02-01&num=10000&f=csv&token=%3Ctoken
The csv output file (auditLog.csv) have empty rows. Is there any alternative to obtain a tracking report?
Thanks,
S.
Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
