With the support for publishing arbitrary values from HTTP stats publishing valve side (or from MSF4J publishing), we can cater this requirement. We will be including this for the M1 of AS 6.0.
For the visualization part (dashboard and gadgets) we will not include any of these arbitrary value processing and provide only generic gadgets. AppCloud can then customize them to process these values to show in their dashboard. We come up with the better name for this prefix. And normally, ALL_CAPS for env variables as the best practice. On Mon, Apr 4, 2016 at 2:59 PM, Kalpa Welivitigoda <[email protected]> wrote: > Hi Pirinthapan, > > As per the offline chat we had, this is being implemented and tracked with > [1]. About the prefix, how about we using "WSO2_" as the prefix. > WSO2_TENANT_ID seems to make more sense. WDYT? > > [1] https://wso2.org/jira/browse/WSAS-2225 > > On Mon, Apr 4, 2016 at 1:17 PM, Pirinthapan Mahendran < > [email protected]> wrote: > >> Hi all, >> >> In AppCloud we will be having the HTTP Monitoring dashboards to showing >> the statistics of the application usages. To accomplish this, we will be >> using the data publishers shiped with msf4j and AS-6.0.0. But still we need >> to publish some AppCloud specific data (i.e : Application Name, Application >> Version, etc.) and tenant id from these publishers to DAS. >> >> To publish these custom data we have come with the following solution, >> which requires some modification in the msf4j and AS publishers. >> >> *When creating the containers during the application deployment, AppCloud >> will set these custom data as Environment Variables. These environment >> variables are prefixed with the keyword 'arbitrary'. * >> >> *e.g : If we are setting application name as an environment variable, the >> key of this environment variable will looks like >> 'arbitrary_applicationName'.* >> >> *Then during the publishing time, the msf4j or AS will read all the >> environment variables with the prefix 'arbitrary' and publish them as >> arbitrary attributes to DAS.* >> >> *The stream definition in the DAS will be configured to capture these >> arbitrary attributes and use them for its internal processing.* >> >> In order to implement this solution we are planning to add these changes >> to the next releases of msf4j and AS with the coordination of msf4j and As >> teams. >> >> If you have any comments on the above solution, we are kindly >> appreciating them. >> >> Thanks & Regards, >> Mahendran Pirinthapan >> Software Engineer | WSO2 Inc. >> Mobile +94772378732. >> > > > > -- > Best Regards, > > Kalpa Welivitigoda > Software Engineer, WSO2 Inc. http://wso2.com > Email: [email protected] > Mobile: +94776509215 > -- *Kishanthan Thangarajah* Associate Technical Lead, Platform Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com <http://kishanthan.wordpress.com>* Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
