All logs are housed in their respective Docker containers, you can see individual logs per container by executing docker ps to get the container id for your desired container, and then docker logs [container-id] to view the logs in that container.  

The Quill Proxy container log from the server can be used to track things like IP addresses that hit the Quill API, # of stories written, and the types of stories that are written. The calls made to the Quill services can be parsed using something like Splunk, for example, to aggregate the calls made to the Quill services.

The log can be redirected to a file by executing docker logs [container-id] > [filename].txt for easier review and parsing. 

For quick viewing on the Quill server, the log command can be filtered to the specific Quill API call you're wanting to review.

  • docker logs [container-id] | grep POST
  • docker logs [container-id] | grep 'GET /v1/'

Parsing Info:

  1. When a dashboard is opened containing the extension there is a "GET /v1/" call made. Looking at the unique IP addresses of those calls can give an idea of how many users are accessing the dashboard.
  2. When a story is written a "POST /v2/stories" call will be made and these can be used to track the user behavior showing how often they are interacting with the extension.  Multiple POST calls would indicate user activity as there will always be at least one "POST" call when the dashboard is opened.
  3. The POST calls can also indicate the type of story being used in the extension, i.e. barchart vs linechart.
    1. Example: "POST /v2/stories/barchart?"