Modeling Firebase app logs

AutomateDV (formerly known as dbtvault)
, ,
1

We working on modeling out Android App Logs. Android Apps can be used across multiple devices by the same user.

We have hub_app, hub_user and hub_screen_id. screen_id is a unique ID of the screen which was opened by the user.

In our case the session is defined by the continuous use of the app without a gap of 30 or more. Session is not tied user opening or closing the app. We perform sessionization in the log repo. Also if the user is using the app or more than 1 device, the session ids will be unique. Session IDs are unique, sequential / user.

Since this is app logs, we are thinking of modeling this as Transactional Link hanging from hub_app, hub_user, hub_screen_id. src_eff will be datetime (minute grain) when the user opens a screen.

Question(s):

  1. Is session_id a Dependent Child in this LINK? We have situations where the user opens the same screen on more than one device within the same minute due to the nature of the app
  2. How do we configure the AutomateDV Transactional Link macro to make use of the session id as a dependent child?

Thanks.

2

sounds like session is an event between three entities or maybe two.

  • app
  • user
  • screen (if this has details of value you’d want to track)

event:

  • session, store the session id as a dep-key in a link-satellite off this interaction, i.e. not in the link itself.
3

Hi @patrickcuba . I am thing of making this a Transaction Link. Can I store the Dependent Child in the TLINK?

4

Ok then,
How is a t-link (although deprecated) with a dep-key different to a link-satellite with dep-key?
Better yet, if you do not create hash keys I think they would look identical except in name.

5

Hi @patrickcuba . Are t-links deprecated?

6

ages ago, you didn’t know?

7

@patrickcuba . I just checked the DV 2.1 specs. Non-historized Links (Non-delta driven links) aka Transactional Links are still in the spec.

8

It’s made a comeback has it?
So how is it different to what I described?

9

With the Non-historized Link we can put all the descriptive attributes in the TLINK itself. And since it is non-delta driver, we don’t need to calculate / compare the hashdiff making it suitable for high velocity data like the firebase app logs.

10

Put the NH link in the t-Link… what?