Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spike: Define specification and scope to configure Content Analytics and perform raw BE queries on the data #29477

Closed
3 of 4 tasks
Tracked by #29475
john-thomas-dotcms opened this issue Aug 6, 2024 · 1 comment

Comments

@john-thomas-dotcms
Copy link
Contributor

john-thomas-dotcms commented Aug 6, 2024

Parent Issue

#29475

Task

Currently, when any Experiment is running, dotCMS stores an event every time any URL on the site is visited.

  • This is less than ideal, but is acceptable for Experiments because on most customer systems, Experiments don't run all the time.
  • However, when Content Analytics (CA) is implemented, this will no longer be acceptable, because CA will be running all the time.

So, we need to provide options to limit where and/or how CA data is collected.

  • For example, we may want to allow users to enable or disable collection of CA data on specific pages/content, particular paths, or different content types.

In order to enable this kind of configuration, we will need a CA App

  • Note: This may need to be separate from the existing Analytics App.

We should (but not must) also provide an interface to allow queries against the CA data from the dotCMS BE UI.

This spike is to:

  • Determine whether we should have a separate CA App, or add config to the existing Analytics App.
  • Scope the work needed to create or update the App.
  • Scope he work would required to provide a basic (bare-bones) CA portlet that enables:
    • Sending a (raw) query to the analytics infrastructure
    • Displaying the results in a readable list

Proposed Objective

Same as Parent Issue

Proposed Priority

Same as Parent Issue

Acceptance Criteria

Cards created for both:

  • Creating or updating the App to allow configuring CA parameters.
  • Creating a basic CA portlet.

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

Tasks

  1. Merged QA : Passed Internal Team : Falcon Type : New Functionality dotCMS : Analytics
  2. Next Release QA : Approved QA : Passed Internal Team : Falcon Type : New Functionality dotCMS : Analytics
  3. Merged QA : Passed Internal Team : Falcon Type : New Functionality dotCMS : Analytics
  4. QA : Passed Internal Team : Falcon Type : New Functionality dotCMS : Analytics
@freddyDOTCMS
Copy link
Contributor

Here the Documentation where I explain what we need to do here

https://docs.google.com/document/d/1g5ta7y7yidlgxh3H88F_TNXnNWpjb-Yp6SfebpHKtCU/view#heading=h.yow0ow19galg

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

3 participants