[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wsf-java-dev
Subject:    Re: [Dev] [EI-Analytics] 'EIAnalyticsHorizontalBarChart' widget shows data only from the ''MINUTE'' 
From:       Ishara Ilangasinghe <isharai () wso2 ! com>
Date:       2018-11-29 8:59:25
Message-ID: CALoSMmE3HpNkGpe4LJs9FpjVbP5pKLz4h9WJmmR-eN8A9Fr8gg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


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: isharai@wso2.com <isharai@wso2.com>*
*Mobile: +94719718288*


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


On Mon, Nov 26, 2018 at 11:40 PM Tharindu Bandara <tharindub@wso2.com>
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 <rolandh@wso2.com> 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/or \
> > g.wso2.analytics.solutions.ei.analytics/widgets/EIAnalyticsHorizontalBarChart/src/resources/widgetConf.json
> >  
> > [2]
> > https://github.com/wso2/analytics-solutions/blob/master/components/ei-analytics/or \
> > g.wso2.analytics.solutions.ei.analytics/widgets/EIAnalyticsSearchBox/src/resources/widgetConf.json
> >  
> > 
> > <https://github.com/wso2/analytics-solutions/blob/master/components/ei-analytics/o \
> > rg.wso2.analytics.solutions.ei.analytics/widgets/EIAnalyticsSearchBox/src/resources/widgetConf.json>
> >  Best Regards,
> > Roland Hewage
> > 
> 
> 
> --
> *Tharindu Bandara*
> Software Engineer | WSO2
> 
> Email : tharindub@wso2.com
> 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
> 


[Attachment #5 (text/html)]

<div dir="ltr">Hi Roland,<div><br></div><div>As per the offline discussion with \
Niveathika, I created [1] to track the issue of &quot;EIAnalyticsSearchBox&quot; \
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 &quot;EIAnalyticsSearchBox&quot; widget.  \
</div><div><br></div><div>Once these changes are merged your concerns related to \
EIAnalyticsSearchBox widget will get solved.</div><div><br></div><div>[1]<a \
href="https://github.com/wso2/analytics-solutions/issues/191">https://github.com/wso2/analytics-solutions/issues/191</a></div><div>[2]<a \
href="https://github.com/wso2/analytics-solutions/pull/192">https://github.com/wso2/analytics-solutions/pull/192</a></div><div><br></div><div><div><div><div><div \
dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div \
dir="ltr"><div><div dir="ltr"><div><div><b>Thanks,<br></b></div><div><div><b><br></b></div><div><b>Ishara \
Ilangasinghe<br></b></div></div><div><span \
style="color:rgb(102,102,102)"></span></div><div><b><span \
style="color:rgb(102,102,102)">Associate Software Engineer | \
WSO2<br></span></b></div><div><b><span style="color:rgb(102,102,102)">Email: <a \
href="mailto:isharai@wso2.com" \
target="_blank">isharai@wso2.com</a><br></span></b></div><div><b><span \
style="color:rgb(102,102,102)">Mobile: \
+94719718288</span></b></div></div><div><br></div><br><a \
href="http://wso2.com/signature" target="_blank"><img \
src="http://c.content.wso2.com/signatures/wso2-signature-general.png" \
alt="http://wso2.com/signature"></a><br></div></div></div></div></div><br></div></div></div></div><br><div \
class="gmail_quote"><div dir="ltr">On Mon, Nov 26, 2018 at 11:40 PM Tharindu Bandara \
&lt;<a href="mailto:tharindub@wso2.com">tharindub@wso2.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi \
Roland,<div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">There I note that the \
&quot;EIAnalyticsHorizontalBarChart&quot; widget&#39;s fetch query [1] is hardcoded \
to &quot;minute&quot; granularity although the Date Time Range Filter consists of a \
granularity selector. So if there is no any specific reason to hardcode it to \
&quot;minute&quot; granularity, may I fix the fetch query to filter according to the \
value of the granularity selector<br></blockquote><div><br></div><div>+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.</div><div><br></div><div>Thanks,</div><div>Tharindu.</div></div><br><div \
class="gmail_quote"><div dir="ltr">On Mon, Nov 26, 2018 at 6:03 PM Roland Hewage \
&lt;<a href="mailto:rolandh@wso2.com" target="_blank">rolandh@wso2.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr">Hi \
all,<br><br>I&#39;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 &amp; \
MediatorStatPerDay tables because we ignore PerHour, PerMinute &amp; 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 \
&quot;minute&quot; granularity. There I note that the \
&quot;EIAnalyticsHorizontalBarChart&quot; widget&#39;s fetch query [1] is hardcoded \
to &quot;minute&quot; granularity although the Date Time Range Filter consists of a \
granularity selector. So if there is no any specific reason to hardcode it to \
&quot;minute&quot; granularity, may I fix the fetch query to filter according to the \
value of the granularity selector. Further I note that the \
&quot;EIAnalyticsSearchBox&quot; widget&#39;s fetch query [2], query from \
ESBStatAgg_MINUTES &amp; MediatorStatAgg_MINUTES tables for a componentName. This can \
be done using ESBStatAgg_DAYS &amp; MediatorStatAgg_DAYS tables too. I couldn&#39;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 &amp; MediatorStatAgg_DAYS tables. The EI Analytics \
dashboard works perfectly fine for migrated PerMinute tables but it&#39;s better to \
consider PerDay tables in a migration. <br><br>Your thoughts on the matter are \
appreciated. <br><br>[1] <a \
href="https://github.com/wso2/analytics-solutions/blob/master/components/ei-analytics/ \
org.wso2.analytics.solutions.ei.analytics/widgets/EIAnalyticsHorizontalBarChart/src/resources/widgetConf.json" \
target="_blank">https://github.com/wso2/analytics-solutions/blob/master/components/ei- \
analytics/org.wso2.analytics.solutions.ei.analytics/widgets/EIAnalyticsHorizontalBarChart/src/resources/widgetConf.json</a><br><br>[2]<a \
href="https://github.com/wso2/analytics-solutions/blob/master/components/ei-analytics/ \
org.wso2.analytics.solutions.ei.analytics/widgets/EIAnalyticsSearchBox/src/resources/widgetConf.json" \
target="_blank"> https://github.com/wso2/analytics-solutions/blob/master/components/ei \
-analytics/org.wso2.analytics.solutions.ei.analytics/widgets/EIAnalyticsSearchBox/src/resources/widgetConf.json \
<br></a><br>Best Regards,</div><div>Roland Hewage<br></div></div> \
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" \
class="m_5151743228909725386gmail_signature" data-smartmail="gmail_signature"><div \
dir="ltr"><span style="text-align:left" dir="ltr"><b>Tharindu Bandara</b><br>Software \
Engineer | WSO2<br><br>Email : <a href="mailto:tharindub@wso2.com" \
target="_blank">tharindub@wso2.com</a> <br>Mobile : +94 714221776<br>web : <a \
rel="nofollow noreferrer" \
href="https://www.google.com/url?q=http://wso2.com&amp;sa=D&amp;ust=1517653383990000&amp;usg=AFQjCNFggB4bSJTKmdqKcBV0VY9xx1ABKg" \
dir="ltr" target="_blank">http://wso2.com</a><br><br></span><a \
href="https://wso2.com/signature" target="_blank">https://wso2.com/signature</a><img \
src="http://c.content.wso2.com/signatures/wso2-signature-general.png"><br></div></div>
 </blockquote></div>



_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic