The Distributed Message Tracer List Widget fails to show data

[nadundesilva]

Description:
The Distributed Message Tracer's List Widget fails to load data. This is due to the table created by Siddhi having camel case column names while the widget expects the data to have upper case column names. This causes the widget to fail to show the data in the table.

Suggested Labels:
Type/Bug

Suggested Assignees:
@ramindu90, @ksdperera

Affected Product Version:
SP 4.2.x, SP 4.3.0

OS, DB, other environment details and versions:
N/A

Steps to reproduce:

• Setup the Stream Processor and point to an external DB (eg:- MySQL).
• Run the Message Tracer and publish data into it.
• Open the dashboard and open the Distributed Message Tracer.
• Click Search to load data.
• Notice that the table is not populated and there are errors in the browser console.

Related Issues:
N/A

[niveathika]

Data provider of the widget needs to be changed to SiddhiAppDataProvider to generalise the query,
https://github.com/wso2/analytics-solutions/blob/master/components/sp-solutions/org.wso2.analytics.solutions.sp.message.tracer/widgets/OpenTracingVisTimeline/src/resources/widgetConf.json#L14

[graziano1955]

I cannot execute the Message Tracer sample in WSO2SP 4.4.0 as in Distributed Message Tracer documentation. After running the siddhi application and the simulation feed, the SpanTable is populated with data. In the Distributed Message Tracer's Search Widget the listboxes are populated with this data but when I click the Search button the Distributed Message Tracer's List Widget fails to load data with this errors:

bundle.js:110 [DEPRECATED] Widget 'OpenTracingSearch' extends from a deprecated version of the Widget (@wso2-dashboards/widget) class. Please use the newest version.

bundle.js:110 [DEPRECATED] Widget 'OpenTracingList' extends from a deprecated version of the Widget (@wso2-dashboards/widget) class. Please use the newest version.

bundle.js:126 Error: Unknown column name defined in the chart config.
at eval (eval at (bundle.js:98), :33:745707)
at Array.forEach ()
at eval (eval at (bundle.js:98), :33:745629)
at Array.forEach ()
at e.value (eval at (bundle.js:98), :33:745599)
at e.value (eval at (bundle.js:98), :33:744738)
at $o (bundle.js:126)
at Qo (bundle.js:126)
at Uo (bundle.js:126)
at jo (bundle.js:126)

Is there a workaround for this problem?