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

Reporting for Analytics engine #521

Open
abramvandergeest opened this issue Dec 11, 2019 · 0 comments
Open

Reporting for Analytics engine #521

abramvandergeest opened this issue Dec 11, 2019 · 0 comments

Comments

@abramvandergeest
Copy link
Contributor

Current behavior:
Reporting is only done by explicitly calling a log / sql activity. Makes it difficult to document each step in the process.

Expected behavior:
Add a layer to the base Activity that optionally allows reporting of the activity input/processing/output to an outside source (Log,SQL,SMS,etc.) that could be configured separately (i.e. in its own section of the JSON)

What is the motivation / use case for changing the behavior?
One example is for A/B testing, where it would be good to report input / A/B choice / and result.

Additional information you deem important (e.g. I need this tomorrow):
Does we use "logging activities" plugged into a root level logging key/value in the JSON? Does the logging key have its own builtin logging functions.

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

No branches or pull requests

3 participants