Activity Log for User | Community
Skip to main content
J
juan_josé_casa1
Level 2
October 16, 2015
Solved

Activity Log for User

  • October 16, 2015
  • 2 replies
  • 1314 views

Hello,

I need to implement an activity log for my public users, I'm planning to generate a node structure like the following:

/home/users/{APP}/{USER}/log/{YEAR}/{MONTH}/{ACTIVITY NODES}

I would like to check with you if find any drawbacks into this implementation.

And also if there is any way to improve the performance of the queries to "log" child nodes in the structure, like indexes, that you could advice me.

Thanks in advance!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by PaulMcMahon

Depending on how active your users are and how granular your tracking is you might want more directories below the month node (you probably don't want more than a couple hundred child nodes of any one directory. 

You will also want to make sure you account unique node names across publish instances - some kind prefix for different nodes. 

One thing you could do to improve query performance is to create a custom mix-in type that you assign to your activity nodes. That will let you narrow your queries in the most effective manner. 

2 replies

P
PaulMcMahonAccepted solution
Level 8
October 16, 2015

Depending on how active your users are and how granular your tracking is you might want more directories below the month node (you probably don't want more than a couple hundred child nodes of any one directory. 

You will also want to make sure you account unique node names across publish instances - some kind prefix for different nodes. 

One thing you could do to improve query performance is to create a custom mix-in type that you assign to your activity nodes. That will let you narrow your queries in the most effective manner. 

J
juan_josé_casa1Author
Level 2
October 16, 2015

orotas wrote...

Depending on how active your users are and how granular your tracking is you might want more directories below the month node (you probably don't want more than a couple hundred child nodes of any one directory. 

You will also want to make sure you account unique node names across publish instances - some kind prefix for different nodes. 

One thing you could do to improve query performance is to create a custom mix-in type that you assign to your activity nodes. That will let you narrow your queries in the most effective manner. 

 

Orotas, Thanks for your help!

Do you have any useful link for the mix-in types used to improve performance ? I don't have experience working with Mix-in types.

Thanks in advance!

Terms & ConditionsAccessibility statement

Loading footer...