IBM Watson™ Ideas

Welcome to the IBM Watson™ Ideas Portal


We welcome and appreciate your feedback on IBM Watson™ Products to help make them even better than they are today!


If you are looking for troubleshooting help or wondering how to use our products and services, please check the IBM Watson™ documentation. Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.


Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal.


If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.

Include Query parameter in results from the query and event log

When we query the /logs for a particular query ID, we can get the natural_language_query paratmer returned which contains the query string.

{ customer_id: '',
environment_id: 'XXXX',
natural_language_query: 'are there any capital metrics?',
query_id: 'XXXX',
document_results: [Object],
event_type: 'query',
session_token: 'XXXXX',
created_timestamp: '2019-04-03T12:02:07.145Z'

This does not work for DQL queries. i.e. we do not get the query parameter returned.

{ customer_id: '',
environment_id: 'XXXX',
query_id: 'XXXX',
document_results: [Object],
event_type: 'query',
session_token: 'XXXXX',
created_timestamp: '2019-04-03T12:02:07.145Z'

 

Could this be added to the results.

  • Guest
  • Apr 3 2019
  • Future Consideration
Why is it useful?
Who would benefit from this IDEA? As a customer I want to be able to monitor usage of DQL queries as well as Natural Language queries
How should it work?
Idea Priority
Priority Justification
Customer Name
Submitting Organization
Submitter Tags
  • Attach files
  • Admin
    JOHN PECORARI commented
    03 Apr 16:31

    What are you trying to achieve, or problem is the customer trying to solve by adding events for DQL queries as well?

  • PATRICK CURTIN commented
    04 Apr 09:49

     The customer has a repeatable process where they will create a new collection with new documents and search/analyse this collection.  There will be '000s of collections created per year.  As the process is repeatable we have a UI with ~100 prebuilt queries that will be run against the collection and there is the ability for the user to create both NLQ and DQL queries.  We want to be able to monitor the usefulness of the prebuilt queries through documents returned and click events.  We want to be able to view the user created queries to check for common queries which will be added to the prebuilt query list.  This will also provide feedback for the WKS models we have created.