Hi all, +1 for coming up with a better name.
@Kalpa, Since this is a generalised solution, if a user want to publish their own environment variables, they can also use this feature. So its better to have some other generalised name rather than "WSO2_". What about the prefix "CUSTOM_"? Thanks, Pirinthapan Mahendran Pirinthapan Software Engineer | WSO2 Inc. Mobile +94772378732. On Mon, Apr 4, 2016 at 3:20 PM, Afkham Azeez <[email protected]> wrote: > Yes, looks like "arbitrary" is a concept in DAS but it doesn't make sense > to name env vars like that. > > 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 >> > > > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>* > *email: **[email protected]* <[email protected]> > * cell: +94 77 3320919 <%2B94%2077%203320919>blog: * > *http://blog.afkham.org* <http://blog.afkham.org> > *twitter: **http://twitter.com/afkham_azeez* > <http://twitter.com/afkham_azeez> > *linked-in: **http://lk.linkedin.com/in/afkhamazeez > <http://lk.linkedin.com/in/afkhamazeez>* > > *Lean . Enterprise . Middleware* >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
