Watson Marketing Ideas
Submit new product ideas for Campaign, Interact, Marketing Operations, Marketing Platform, Campaign Managed Hosted, interact Managed Hosted, Marketing Operations Managed Hosted, Digital Analytics, Tealeaf, Universal Behavior Exchange, Watson Customer Experience Analytics, Watson Marketing Insights, Watson Content Hub, Web Content Manager and WebSphere Portal solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed.
Connect with your peers and IBM experts on the Watson Marketing and Commerce Community
Submit ideas for other Watson Customer Engagement Products:
• Watson Campaign Automation
• Watson Commerce
• Watson Supply Chain
Tealeaf session indexing can be very costly, with index storage size commonly being twice session (LSSN) storage size, and sometimes escalating to far more. More control is required to skip indexing on content that is not meaningful for session search.
Tealeaf currently provides a mechanism for adding content types to index (i.e., "Additional Content Types to Index"), but the opposite type of control is also needed.
These options are requested, for identifying hits to skip:
A workaround has been deployed from time to time... to "munge" the content type and have the indexer skip the hit, but this sometimes interferes with replay.
For reference, these content types are indexed by default:
A hit designated to to be "skipped" for indexing would disregard these defaults, and not be indexed.
When a hit is "skipped" for indexing, standard request indexing would still be done, but the response and any JSON or XML payload in the request would not be indexed. This will help materially in AJAX heavy applications, where those data elements are not expected to be searched for directly.
Additionally, if the DTSearch engine supports compression, and it is not already in use, enabling compression might reduce storage size. However, uncompressed storage has a storage advantage when the media supports de-duplication, so compression should also be disable-able.
How will this idea be used?
Reducing the storage cost for Tealeaf improves it's value proposition, and helps with scalability. Additionally, reducing the indexing workload avoids indexing backlogs, and makes completed session searchable earlier.
|What is your industry?||Telecommunications|
|What is the idea priority?||Medium|
|Link to original RFE|