libosmocore.git branch jerlbeck/wip/stats updated. 0.9.0-15-gcd7a5c0

gitosis at osmocom.org gitosis at osmocom.org
Mon Nov 9 13:20:39 UTC 2015


This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "An utility library for Open Source Mobile Communications".

The branch, jerlbeck/wip/stats has been updated
  discards  749952e90fd40d3a6bf17ac173d890f2fadbc4c8 (commit)
  discards  872d8aeea0cf3c2d12dca5d30940e02daba33562 (commit)
  discards  7c3f729db2c33842c2dad702dfe4251dea4a06be (commit)
  discards  e007a9ee8bc59d04cb1672df0e3c8ab32001f0d7 (commit)
  discards  a328503f309d8e0424d996c68c96b9e9072da230 (commit)
       via  cd7a5c069e96a747ef27536e250e582c97828863 (commit)
       via  9872b4b70497773c2632931e55cc8830526b86b2 (commit)
       via  c79eae2c6113cca531bf19350ea11f7a84caac16 (commit)
       via  916423ef9585c7042730fdb17f55afc376565d32 (commit)
       via  834819471a024a98cf6062f1e20c75a9b9e26f88 (commit)
       via  aab4a2497c59d83c396881aaa661a054978f8f7c (commit)
       via  eed4695d062a64c78340d24d53ae7066e6c7c1fd (commit)
       via  495b0dbd24627a9289e9bdb8ef2f80af6af3445f (commit)
       via  6e149b1f1aceb86e694e090b5ba4ccb349edcbf2 (commit)
       via  59b90bc44401dc0e4c5004b0fec677106bce8871 (commit)
       via  fed2a488b94fc24df4f5548f98a71bb98920a66a (commit)
       via  be37fb7db4651f245994fa73008b4aa92c21c14f (commit)
       via  ca6602f476775e1b55c5a1d41bc323c49b9e4290 (commit)
       via  ee2657f6af4b81f98cfdfd900a82d9a350ff3642 (commit)

This update added new revisions after undoing existing revisions.  That is
to say, the old revision is not a strict subset of the new revision.  This
situation occurs when you --force push a change and generate a repository
containing something like this:

 * -- * -- B -- O -- O -- O (749952e90fd40d3a6bf17ac173d890f2fadbc4c8)
            \
             N -- N -- N (cd7a5c069e96a747ef27536e250e582c97828863)

When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
http://cgit.osmocom.org/libosmocore/commit/?id=cd7a5c069e96a747ef27536e250e582c97828863

commit cd7a5c069e96a747ef27536e250e582c97828863
Author: Jacob Erlbeck <jerlbeck at sysmocom.de>
Date:   Mon Nov 9 14:13:23 2015 +0100

    stats: Fix not reported stat item values
    
    Currently the global stat item index is being advanced in
    osmo_stat_item_group_handler, so that the second and further groups
    in the list will skip new item values.
    
    This commit moves the call to osmo_stat_item_discard_all into
    osmo_stats_report to a place where all groups have been processed
    already.
    
    Sponsored-by: On-Waves ehf

http://cgit.osmocom.org/libosmocore/commit/?id=9872b4b70497773c2632931e55cc8830526b86b2

commit 9872b4b70497773c2632931e55cc8830526b86b2
Author: Jacob Erlbeck <jerlbeck at sysmocom.de>
Date:   Mon Nov 9 11:39:42 2015 +0100

    stats: Fix handling of multiple resporters
    
    Currently the reporter loop is aborted, if the event would be ignored
    due to an insufficient max_level. Thus the reporters that happen to
    be stored afterwards would be skipped even if their level were
    sufficient.
    
    This commit replaces the conditional 'return' statement by a
    considtional 'continue' statement to ensure the processing of the
    list tail.
    
    Sponsored-by: On-Waves ehf

http://cgit.osmocom.org/libosmocore/commit/?id=c79eae2c6113cca531bf19350ea11f7a84caac16

commit c79eae2c6113cca531bf19350ea11f7a84caac16
Author: Jacob Erlbeck <jerlbeck at sysmocom.de>
Date:   Mon Nov 9 11:25:12 2015 +0100

    stats: Send all values on reporter update
    
    Currently only counter changes and new item values are being
    reported. This makes it cumbersome to configure reporting clients,
    since there is nothing like a list of all parameters.
    
    This commit changes this behaviour such that all currently existing
    counters and items that would be reported eventually, are passed to
    the reporter when it has been reconfigured or enabled.
    
    Note that this will not catch transient counters/items that will be
    created later on, e.g. triggered by new peers or subscribers.
    
    To just force this kind of dump on a running reporter, it is
    sufficient to invoke the 'enable' command in its configuration node.
    
    Sponsored-by: On-Waves ehf

-----------------------------------------------------------------------

Summary of changes:
 debian/changelog                 | 12 +++++++
 include/osmocom/core/rate_ctr.h  |  5 +++
 include/osmocom/core/stat_item.h |  6 ++++
 include/osmocom/core/stats.h     |  1 +
 src/gb/gprs_ns.c                 |  2 ++
 src/stats.c                      | 67 +++++++++++++++++++++++++++-------------
 src/vty/stats_vty.c              |  1 +
 utils/osmo-sim-test.c            |  1 +
 8 files changed, 73 insertions(+), 22 deletions(-)


hooks/post-receive
-- 
An utility library for Open Source Mobile Communications



More information about the osmocom-commitlog mailing list