Details

    • Backport:
      No
    • Backward Breaking:
      No
    • # Replies:
      7
    • Last comment by Customer:
      true
    • Documentation changes needed?:
      Yes

      Description

      Issues to bring together metric and stats related changes for making the server better instrumented and increase visibility into internal rates/metrics.

        Issue Links

          Activity

          Hide
          Scott Hernandez
          added a comment -

          Other ideas:

          Most frequent/slowest by period:

          • Slowest ops per coll/db by type (top N/Mmin)
          • Highest occurrence by query template (top N/Mmin)
          • Most used indexes (top N/Mmin)

          ...

          Show
          Scott Hernandez
          added a comment - Other ideas: Most frequent/slowest by period: Slowest ops per coll/db by type (top N/Mmin) Highest occurrence by query template (top N/Mmin) Most used indexes (top N/Mmin) ...
          Hide
          Scott Hernandez
          added a comment -

          Other notes/ideas from 5/11/12 meeting:

          Track counters by source (mongos or direct, user initiated, system – repl/shard-cmd --, localhost/ip, user)

          Ind. cmd (types) by coll/db – like count, aggregate, mapReduce, drop/etc

          Histograms/buckets by costs/latency and variance for things

          Need nano/microsecs timing with reporting in fractions of ms/micros

          Track extent stuff, freelist/etc., create/delete, per file

          Data size w/without padding.

          Maybe track possible faults per ns.

          Track network related stats: create/destroy, socket exceptions, outgoing bytes, buffer bytes, sockets stats (ops, bytes, stack usage)

          BSON* operations: iteration, append, realloc, copy

          Update operations: ex $addToSet/$pull/$etc.

          How to answer if fragment exists and compact is needed.

          Show
          Scott Hernandez
          added a comment - Other notes/ideas from 5/11/12 meeting: Track counters by source (mongos or direct, user initiated, system – repl/shard-cmd --, localhost/ip, user) Ind. cmd (types) by coll/db – like count, aggregate, mapReduce, drop/etc Histograms/buckets by costs/latency and variance for things Need nano/microsecs timing with reporting in fractions of ms/micros Track extent stuff, freelist/etc., create/delete, per file Data size w/without padding. Maybe track possible faults per ns. Track network related stats: create/destroy, socket exceptions, outgoing bytes, buffer bytes, sockets stats (ops, bytes, stack usage) BSON* operations: iteration, append, realloc, copy Update operations: ex $addToSet/$pull/$etc. How to answer if fragment exists and compact is needed.
          Hide
          Scott Hernandez
          added a comment -

          Add counters about query planner (multiplan execution) and how often it is run on each collection/index.

          Show
          Scott Hernandez
          added a comment - Add counters about query planner (multiplan execution) and how often it is run on each collection/index.
          Hide
          Scott Hernandez
          added a comment -

          Add counters to track documents touched/returned grouped by opcounter, and total.

          For example, this would allow us to answer the number of documents affected by queries/updates/removes/commands/etc.

          Show
          Scott Hernandez
          added a comment - Add counters to track documents touched/returned grouped by opcounter, and total. For example, this would allow us to answer the number of documents affected by queries/updates/removes/commands/etc.
          Hide
          Scott Hernandez
          added a comment -

          Track min/max/avg ms per query (template) or index; maybe easier to track this at the collection level for all queries on that collection to start with.

          Show
          Scott Hernandez
          added a comment - Track min/max/avg ms per query (template) or index; maybe easier to track this at the collection level for all queries on that collection to start with.
          Hide
          Dan Pasette
          added a comment -

          Author:

          {u'date': u'2012-10-26T15:12:12-07:00', u'name': u'Eliot Horowitz', u'email': u'erh'}

          Message: SERVER-5828 - rewrite sererStatus caommands to be modular
          allow any code to register sections or metrics without touching core code
          have same core serverStatus code for mongos and mongod
          Branch: master
          https://github.com/mongodb/mongo/commit/b56566bf0ec3cb00221e8e951b24f47783ec2af3

          Show
          Dan Pasette
          added a comment - Author: {u'date': u'2012-10-26T15:12:12-07:00', u'name': u'Eliot Horowitz', u'email': u'erh'} Message: SERVER-5828 - rewrite sererStatus caommands to be modular allow any code to register sections or metrics without touching core code have same core serverStatus code for mongos and mongod Branch: master https://github.com/mongodb/mongo/commit/b56566bf0ec3cb00221e8e951b24f47783ec2af3
          Hide
          Grégoire Seux
          added a comment -

          This would be really great to gain more dba support toward mongodb. Right now tooling and metrics are at a bare minimum.

          Show
          Grégoire Seux
          added a comment - This would be really great to gain more dba support toward mongodb. Right now tooling and metrics are at a bare minimum.

            People

            • Votes:
              8 Vote for this issue
              Watchers:
              18 Start watching this issue

              Dates

              • Created:
                Updated:
                Days since reply:
                1 year, 16 weeks, 6 days ago
                Date of 1st Reply: