How do we understand whether a Lobby Dashboard is used or not by users?

Hi @hhy38 I’ve also been thinking about this for some time. The best idea I have come up with is to use the raw apache logs that are generated and somehow tie that in with the URL that is generated by the unique ID of the lobby. Based on this you should be able to see the last time the URL was accessed and therefore understand if the are in/out of use. 

We ended up writing a PL/SQL package that logged to a custom table.
Then added an element to each Lobby that called the API to write the log.

and then reported on that.

Hi @KIMKIMANDREW,
That’s look like very smart. Thank you. I will try to apply and I will turn back. 

@hhy38 I like it, do you write to a custom LU? or some database alert log?

@david.harmer Probably, I will prefer to write an API. Because, we don’t need to see the logs on the application.  

@KIMKIMANDREW Hi,

I prepared a function. Functions don’t allow to perform DML operation. How did you solve it?

Regards,

Hasan

Hi Damith @dsj 

Do you have any suggestion?

Hi @hhy38 

I suppose if you use PRAGMA AUTONOMOUS_TRANSACTION; in the function, then you could avoid this error. However, I think monitoring the http logs as  @david.harmer suggested would be a better approach for such a requirement.

 Cheers!

Damith

Damith thank you.

I don’t have any knowledge about monitoring http logs. If I can’t solve it. I will use this way.

when I write PRAGMA AUTONOMOUS_TRANSACTION. Some bizarre things happen. It didn’t work before and threw the “ora 06519 active autonomous transaction detected and rolled back” error. After some minutes It worked. I was happy a lot. I changed something in the same API which is not related to this function. Now it is throwing the same error. What happened? I couldn’t understand.

@dsj Damith,

I solved the problem. We must use COMMIT with PRAGMA AUTONOMOUS_TRANSACTION. I am happy again. :)

Thank you all. The function adds logs to the custom page.