Last modified: 2014-02-26 12:53:42 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T63076, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 61076 - Subscriber support in JSON schemas
Subscriber support in JSON schemas
Status: NEW
Product: Analytics
Classification: Unclassified
EventLogging (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2014-02-08 00:53 UTC by Dario Taraborelli
Modified: 2014-02-26 12:53 UTC (History)
9 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Dario Taraborelli 2014-02-08 00:53:19 UTC 
We are starting to see potential instrumentation requests where:

1) the data collected might be unsuitable to be stored into SQL due to (a) the volume of events logged and/or (b) the fact that the analyst may not be using SQL at all to crunch this data. 

2) the data collected needs to be segregated from other logs because it's subject to different privacy terms (for example the Donor Privacy Policy) or data retention conditions (per the Data Retention Guidelines).

Should there be flags in JSON schemas deployed in production to automatically determine what subscriber listens to a specific log?
Comment 1 Andre Klapper 2014-02-26 12:53:42 UTC 
[moving from MediaWiki extensions to Analytics product - see bug 61946]
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links