Ok, thanks. I have you figure some things out but I think it will
probably work.
I'v seen the ticket you submitted. I have no other ideas about this
issue (mainly because I don't have enough knowledge about the command
service yet :-) )
Erik
On 11/02/2014 10:11 AM, Dan Haywood wrote:
On 31 October 2014 08:30, Erik de Hair <[email protected]> wrote:
Hi,
We would like to have statistics about our application use, preferably per
user or at least the customer (related entity) the user is logged in for.
Called actions could be analyzed with results of
@PublishedAction/@Auditing.
Even better for this is to use the combination of Command service and
Auditing. The persisted commands will give you details of every action
invoked by the users, and related to the audit trail. We use this in
Estatio, it gives great traceability. See [1]
But how to use Isis to track visiting entity pages, without losing user
information like when using the servers access log? Would that be possible?
This does sound like a feature we should extend the Command Service to
support. Do raise a ticket for this requirement.
But in the meantime, you could probably use the EventBus and set up a
subscriber for the numerous events that are generated whenever an entity is
rendered. This is very fine-grained information, so you would probably
only want to log for one particular property per entity. But the
information you need should be there.
HTH
Dan
[1] http://isis.apache.org/reference/services/command-context.html
Erik
<mailto:[email protected]>
