I'm wondering if this is a use case for Tamaya Server?  Or would you expect
it inline when reading configuration (e.g. yaml or json).  I don't think
the properties syntax would help much here.

Basically, I share your concerns.  Right now, to achieve the documentation
piece my team maintains a large confluence page with all of the
configuration settings, the defaults, description of where used.  Its very
useful, but hard to follow.

Metrics is less of a concern, since we cache configuration on start up
rather than at runtime.

John

On Fri, Apr 22, 2016 at 12:52 PM Oliver B. Fischer <[email protected]>
wrote:

> Hi,
>
> let me explain the background of the following feature requests before I
> describe them.
>
> Currently I work in a team which is responsible for quite a lot of
> services - I will avoid the term microservices ;-) One problem is the
> configuration and the maintenance  of all the different properties.
> Sometime we can not be sure if we can remove a property or not. How
> should we know if a property is still used or so much the worse a
> property is missing.
>
> Especially in legacy environments we sometimes have some properties we
> don't know and what they are used for.
>
> Both problems can be solved but it takes time.
>
> This is the moment there Tamaya comes in. I would like to see the
> following features in Tamaya.
>
> 1. Statistics: It should be possible to retrieve some statistics for a
> given property. I would like to "ask" Tamaya how often a property has
> been requested.
>
> 2. Inline documentation: It should be possible to add a simple comment
> to a property as description of the property. The description should be
> available via the API.
>
> What do you think about theses possible features? Would they be helpfull
> even for you?
>
> Bye,
>
> Oliver
>
>
> <
> http://dict.leo.org/ende/index_de.html#/search=especially&searchLoc=0&resultOrder=basic&multiwordShowSingle=on
> >
>
>
> --
> N Oliver B. Fischer
> A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
> P +49 30 44793251
> M +49 178 7903538
> E [email protected]
> S oliver.b.fischer
> J [email protected]
> X http://xing.to/obf
>
>

Reply via email to