Hello @Gloria,

there is an Audit log that you can use for such information. https://docs.ataccama.com/one/latest/audit/audit.html To make these statistics, it might be better to use the API: https://docs.ataccama.com/one/latest/one-apis/audit-api.html and aggregate the different logs. Ataccama logs everything and it might be overwhelming.

There is a comment under this article with an example of IDE plan extracting such data from the Audit log:

Also, by default the audit log is enabled only on source and Catalog items. If you want it also for other entities, you need to turn it on using a trait audit:auditEnabled (see the above documentation).

Let me know if this helps.

Kind regards,

Anna

​@anna.spakova Am I reading this correctly that it only tracks changes made to the entities in ONE?

How about login history? Is there some way to extract that too?

Thanks!

Hi ​@may_kwok,

it also tracks the Read operations, so it doesn’t require the actual editing of entities (so if user logs in and enters Catalog, it also creates audit logs),

But I think that we had a usecase internally when the PS was using the Keycloak logs to track the actual logins. I will try to find more details.

Kind regards,

Anna

Hi ​@may_kwok ,

so Keycloak has GET /admin/realms/{realm}/events API call, that can give you all events for a specific client (e.g. one-webapp-public-client) and type (=LOGIN)

https://www.keycloak.org/docs-api/latest/rest-api/index.html

That is the other option our team investigated besides the Audit log.

Kind regards,

Anna