Hi Łukasz, On Wed, 16 Jan 2013 14:54:02 +0100 Łukasz Mierzwa <[email protected]> wrote:
> 2013/1/15 Łukasz Mierzwa <[email protected]> > > > 2. Different namespace > >> Currently carbon plugin does not allow me to put my metrics in > >> arbitrary location (besides I found default metric path a bit too > >> long for my needs). > >> Maybe extra option(?) to allow to override base path for metrics ? > >> > > > > We could use extra options for specificity graphs root. > > > > https://github.com/unbit/uwsgi/pull/119 > > I've added --carbon-root option, usage: --carbon-root "test.ns1" Thank you. > This is now fixed in master branch for both carbon and cheaper > busyness plugin, it should detect such condition and will set > busyness to 100%. > > > > 5. Empty metrics > >> Some of the metrics are generated even though their value is > >> always 0 (eg. rss/vsz) as those only get updated in certain > >> circumstances (enabled resource limiting base don memory footprint > >> or memory usage reporting). In such circumstances I don't think it > >> makes sense to generate them at all. > > > > > https://github.com/unbit/uwsgi/pull/120 From what I see rss/vsz is generated under the following condition: uwsgi.shared->options[UWSGI_OPTION_MEMORY_DEBUG] == 1 || uwsgi.force_get_memusage Might be worth to add uwsgi.force_get_memusage, so we will additionally get metrics when we limit resources based on some memory conditions.. > > 6. Calculation for cheaped / active workers > >> I see that in some cases we calculate some total metrics (regading > >> whole instance) for all (even cheaped) workers and some only for > >> active workers (process is running). > >> I would say that eg. harakiri metric should be counted over all > >> rather than active only workers as it's a counter. > > > > > https://github.com/unbit/uwsgi/pull/120 Thank you. Marcin _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
