Hi Roland,

As per the offline discussion with Niveathika, I created [1] to track the
issue of "EIAnalyticsSearchBox" widget fetching data from aggregations. I
did few modifications[2] to the EI Analytics Siddhi app, so it will
maintain a separate table (ComponentNameTable) which will be used by the
"EIAnalyticsSearchBox" widget.

Once these changes are merged your concerns related to EIAnalyticsSearchBox
widget will get solved.

[1]https://github.com/wso2/analytics-solutions/issues/191
[2]https://github.com/wso2/analytics-solutions/pull/192


*Thanks,*


*Ishara Ilangasinghe*

*Associate Software Engineer | WSO2*

*Email: [email protected] <[email protected]>*
*Mobile: +94719718288*


[image: http://wso2.com/signature] <http://wso2.com/signature>


On Mon, Nov 26, 2018 at 11:40 PM Tharindu Bandara <[email protected]>
wrote:

> Hi Roland,
>
> There I note that the "EIAnalyticsHorizontalBarChart" widget's fetch query
>> [1] is hardcoded to "minute" granularity although the Date Time Range
>> Filter consists of a granularity selector. So if there is no any specific
>> reason to hardcode it to "minute" granularity, may I fix the fetch query to
>> filter according to the value of the granularity selector
>>
>
> +1. Fetch query was initially based on the DAS based widget logic and
> seems like we missed the chance to improve it with data time range filter.
>
> Thanks,
> Tharindu.
>
> On Mon, Nov 26, 2018 at 6:03 PM Roland Hewage <[email protected]> wrote:
>
>> Hi all,
>>
>> I'm doing the project on migration of analytic products from DAS to SP.
>> When considering EI ANALYTICS, I wrote a migration script using Spark SQL
>> to migrate data related to EI Analytics from DAS to SP. I migrated
>> ESBStatPerDay & MediatorStatPerDay tables because we ignore PerHour,
>> PerMinute & PerSecond cases in migration. But I faced certain issues in
>> displaying the migrated data in the EI ANALYTICS dashboard because the
>> fetch query of certain widgets are hardcoded to "minute" granularity. There
>> I note that the "EIAnalyticsHorizontalBarChart" widget's fetch query [1] is
>> hardcoded to "minute" granularity although the Date Time Range Filter
>> consists of a granularity selector. So if there is no any specific reason
>> to hardcode it to "minute" granularity, may I fix the fetch query to filter
>> according to the value of the granularity selector. Further I note that the
>> "EIAnalyticsSearchBox" widget's fetch query [2], query from
>> ESBStatAgg_MINUTES & MediatorStatAgg_MINUTES tables for a componentName.
>> This can be done using ESBStatAgg_DAYS & MediatorStatAgg_DAYS tables too. I
>> couldn't display the migrated data because the fetch query, fetches from
>> the PerMinutes tables which I havent migrated. So if there is no any
>> concerns, may I change the fetch query to query from ESBStatAgg_DAYS &
>> MediatorStatAgg_DAYS tables. The EI Analytics dashboard works perfectly
>> fine for migrated PerMinute tables but it's better to consider PerDay
>> tables in a migration.
>>
>> Your thoughts on the matter are appreciated.
>>
>> [1]
>> https://github.com/wso2/analytics-solutions/blob/master/components/ei-analytics/org.wso2.analytics.solutions.ei.analytics/widgets/EIAnalyticsHorizontalBarChart/src/resources/widgetConf.json
>>
>> [2]
>> https://github.com/wso2/analytics-solutions/blob/master/components/ei-analytics/org.wso2.analytics.solutions.ei.analytics/widgets/EIAnalyticsSearchBox/src/resources/widgetConf.json
>>
>>
>> <https://github.com/wso2/analytics-solutions/blob/master/components/ei-analytics/org.wso2.analytics.solutions.ei.analytics/widgets/EIAnalyticsSearchBox/src/resources/widgetConf.json>
>> Best Regards,
>> Roland Hewage
>>
>
>
> --
> *Tharindu Bandara*
> Software Engineer | WSO2
>
> Email : [email protected]
> Mobile : +94 714221776
> web : http://wso2.com
> <https://www.google.com/url?q=http://wso2.com&sa=D&ust=1517653383990000&usg=AFQjCNFggB4bSJTKmdqKcBV0VY9xx1ABKg>
>
> https://wso2.com/signature
>
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to