Hi Rukshan, AFAIR we added AM_DB to the worker's runtime for the BOT DETECTION feature[1]. Since it is not activated by default, I don't see any other requirement to define it by default. Hence, +1 for removing the AM_DB configuration from the default worker deployment.yaml file.
[1] https://apim.docs.wso2.com/en/latest/Learn/APISecurity/ThreatProtection/bot-detection/ Best regards, Raveen. On Mon, Dec 16, 2019 at 12:05 PM Rukshan Premathunga <[email protected]> wrote: > Hi All, > > API Analytics currently has the following data source configs. > > 1. worker > - WSO2_METRICS_DB > - WSO2_PERMISSIONS_DB > - GEO_LOCATION_DATA > - APIM_ANALYTICS_DB > - WSO2AM_MGW_ANALYTICS_DB > - AM_DB > - WSO2_CLUSTER_DB > 2. dashboard > - WSO2_DASHBOARD_DB > - BUSINESS_RULES_DB > - WSO2_METRICS_DB > - WSO2_PERMISSIONS_DB > - APIM_ANALYTICS_DB > - AM_DB > > In worker runtime, AM_DB is used in a few use cases. Hence we can remove > it from the default configuration to simplify the configuration. > Further, we can merge APIM_ANALYTICS_DB and WSO2AM_MGW_ANALYTICS_DB > databases and configure one DB(as we recommend). > > Hence I think it is better to apply above to the default configurations. > Any suggestions? > > Thanks and Regards > > -- > Rukshan C. Premathunga | Associate Technical Lead | WSO2 Inc. > (m) +94711822074 | (w) +94112145345 | Email: [email protected] > GET INTEGRATION AGILE > Integration Agility for Digitally Driven Business > -- *Raveen Rathnayake* | Software Engineer | WSO2 Inc. (m) +94771144549 | (e) [email protected] <http://wso2.com/signature>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
