Meanwhile found this post [2] by Rukshan, which describes clearly whether
each APIM profile (nodes) require to enable analytics, whether events are
published by each, and whether they read Stats DB. I think such this an
all-in-one table would be nice to be included into WSO2 docs too.

[2] -
http://www.rukspot.com/configure_wso2_apim_analytics_on_cluster_environment.html

Regards,
Samitha

On Wed, Jan 24, 2018 at 10:05 AM, Samitha Chathuranga <[email protected]>
wrote:

> Hi,
>
> Based on your PR you have added stat db for gateway profiles. We don't
>> configure stat db for gateways. Normally we don't specify any databases
>> for gateways unless we have multi-tenancy and google analytics is
>> enabled.
>
> So gateways do not use stat db as analytics events are published to DAS
> (and DAS do the DB write), and gateways do not require to query stats db
> too [1]. I think that is what Pubudu meant. So in this case, we won't need
> to configure stats db datasource for Gateway nodes, hence adding stats db
> related datasource hieradata to those gateway realated yaml file would be
> redundent. This won't break puppet modules, (or no harm to the final
> clustered setups too), but no need to add those configurations.
>
> [1] https://docs.wso2.com/display/AM210/Distributed+Deployment+
> of+API+Manager
>
> Regards,
> Samitha
>
> On Tue, Jan 23, 2018 at 10:50 PM, Chamalee De Silva <[email protected]>
> wrote:
>
>> Hi Pubudu,
>> This is a fix done in order to override the existing common statdb
>> configuration which comes with the common.yaml of each pattern (3,4,5,6) as
>> by default that comes with H2.
>> When we are configuring analytics for a clustered environment, we need to
>> enable stats for gateway worker and events are published to it as well.
>>
>> Publisher/store node already have statdb config in each pattern.
>>
>> What do you mean is it is not required to do the datasource configuration
>> in gateway worker nodes ?
>>
>> @Samitha, appreciate your opinion as well on this.
>>
>>
>>
>> Thanks,
>> Chamalee
>>
>> On Tue, Jan 23, 2018 at 10:28 PM, Pubudu Gunatilaka <[email protected]>
>> wrote:
>>
>>> Hi Chamalee,
>>>
>>> Based on your PR you have added stat db for gateway profiles. We don't
>>> configure stat db for gateways. Normally we don't specify any databases for
>>> gateways unless we have multi-tenancy and google analytics is enabled.
>>>
>>> Thank you!
>>>
>>> On Tue, Jan 23, 2018 at 9:52 PM, Chamalee De Silva <[email protected]>
>>> wrote:
>>>
>>>> [+dev]
>>>>
>>>> On Tue, Jan 23, 2018 at 6:37 PM, Chamalee De Silva <[email protected]>
>>>> wrote:
>>>>
>>>>> Hi all,
>>>>> While working on the documentation issue raised in [1]  I could find
>>>>> out that there is a inconsistency in the data-source URL appeared for
>>>>> WSO2AM_STATS_DB master datasource configuration in puppet-apim patterns.
>>>>> (In default configuration it appears as WSO2AM_STAT_DB as the db name and
>>>>> in mysql configuration of analytics product, it appears as statdb in [2]).
>>>>>
>>>>> Other than that for the patterns where the APIM Analytics is
>>>>> configured (patern 3.4.5 and 6), we haven't added the MySQL master
>>>>> datasource configuration in API Manager side though it is added to the
>>>>> analytics product configuration in [3].
>>>>>
>>>>> As per the offline discussion had with Samitha, I have fixed this by
>>>>> adding the master datasource configuration for the gateway-workers in the
>>>>> patterns where analytics is enabled so that the datasource configuration
>>>>> will be overridden with mysql configuration.
>>>>>
>>>>> Fix is available in PR [4] and [5] for v2.1.0 branch and for the
>>>>> master branch respectively.
>>>>>
>>>>>
>>>>>
>>>>> [1] https://github.com/wso2/product-apim/issues/2340
>>>>> [2] https://github.com/wso2/puppet-apim/tree/master/wso2am_runtime
>>>>> [3] https://github.com/wso2/puppet-apim/blob/master/wso2am_a
>>>>> nalytics/hieradata/dev/wso2/wso2am_analytics/pattern-1/default.yaml
>>>>>
>>>>> [4] https://github.com/wso2/puppet-apim/pull/59
>>>>> [5] https://github.com/wso2/puppet-apim/pull/60
>>>>>
>>>>> --
>>>>> Thanks & Regards,
>>>>>
>>>>> *Chamalee De Silva*
>>>>> Software Engineer
>>>>> *WS**O2* Inc. :http://wso2.com/
>>>>>
>>>>> Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
>>>>> mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Thanks & Regards,
>>>>
>>>> *Chamalee De Silva*
>>>> Software Engineer
>>>> *WS**O2* Inc. :http://wso2.com/
>>>>
>>>> Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
>>>> mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
>>>>
>>>>
>>>
>>>
>>> --
>>> *Pubudu Gunatilaka*
>>> Committer and PMC Member - Apache Stratos
>>> Senior Software Engineer
>>> WSO2, Inc.: http://wso2.com
>>> mobile : +94774078049 <%2B94772207163>
>>>
>>>
>>
>>
>> --
>> Thanks & Regards,
>>
>> *Chamalee De Silva*
>> Software Engineer
>> *WS**O2* Inc. :http://wso2.com/
>>
>> Office   :- *+94 11 2145345 <%2B94%2011%202145345>*
>> mobile  :- *+94 7 <%2B94%2077%202782039>1 4315942*
>>
>>
>
>
> --
> *Samitha Chathuranga*
> *Software Engineer*, *WSO2 Inc.*
> lean.enterprise.middleware
> Mobile: +94715123761
>
> [image: http://wso2.com/signature] <http://wso2.com/signature>
>



-- 
*Samitha Chathuranga*
*Software Engineer*, *WSO2 Inc.*
lean.enterprise.middleware
Mobile: +94715123761

[image: http://wso2.com/signature] <http://wso2.com/signature>
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to