Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-5828

Metric/Stats Tracking

        Details

        • Backwards Compatibility:
          Fully Compatible

          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

            is related to

            New Feature - A new feature of the product, which has yet to be developed. SERVER-5905 Add data collection and command to get histogram of query response times

            • Major - P3 - Major loss of function.
            • Closed

            Improvement - An improvement or enhancement to an existing feature or task. SERVER-1740 track slowest query per minute

            • Major - P3 - Major loss of function.
            • Open

            Improvement - An improvement or enhancement to an existing feature or task. SERVER-1739 trace total nscanned and other query/operation metrics

            • Major - P3 - Major loss of function.
            • Closed

            Improvement - An improvement or enhancement to an existing feature or task. SERVER-4672 add monitoring of version reload statistics to mongos

            • Major - P3 - Major loss of function.
            • Closed

            Improvement - An improvement or enhancement to an existing feature or task. SERVER-7081 Track (new) replication stats

            • Major - P3 - Major loss of function.
            • Closed

            Improvement - An improvement or enhancement to an existing feature or task. SERVER-7382 Track counters for each command

            • Major - P3 - Major loss of function.
            • Closed

            Improvement - An improvement or enhancement to an existing feature or task. SERVER-12172 Add finer granularity metrics for serverStatus

            • Major - P3 - Major loss of function.
            • Closed
            related to

            Epic - Created by JIRA Agile - do not edit or delete. Issue type for a big user story that needs to be broken down. SERVER-2227 Per index access stats

            • Major - P3 - Major loss of function.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. TOOLS-42 Make mongostat configurable

            • Major - P3 - Major loss of function.
            • Resolved

            Improvement - An improvement or enhancement to an existing feature or task. SERVER-2178 Track stats per db/collection

            • Major - P3 - Major loss of function.
            • Open

            Improvement - An improvement or enhancement to an existing feature or task. SERVER-3109 Expose index stats

            • Major - P3 - Major loss of function.
            • Open

            Improvement - An improvement or enhancement to an existing feature or task. SERVER-4897 make JournalStats in ServerStatus counters

            • Major - P3 - Major loss of function.
            • Open

            Improvement - An improvement or enhancement to an existing feature or task. SERVER-13220 Add and expose statistics to new query framework

            • Major - P3 - Major loss of function.
            • Open

            Improvement - An improvement or enhancement to an existing feature or task. SERVER-5173 Track replication getMores separately from client getMores.

            • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
            • Open

            Improvement - An improvement or enhancement to an existing feature or task. SERVER-4202 Add a way to get stats on number of queries that hit an index, per collection

            • Major - P3 - Major loss of function.
            • Closed

            Improvement - An improvement or enhancement to an existing feature or task. SERVER-5787 Track opcounters (insert/delete/update) which results from sharding commands

            • Major - P3 - Major loss of function.
            • Closed

            Improvement - An improvement or enhancement to an existing feature or task. SERVER-5784 Record all btree stats (stop sampling)

            • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
            • Closed

              Activity

              • Comments
              Ascending order - Click to sort in descending order
              Hide
              Permalink
              scotthernandez 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
              scotthernandez 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
              Permalink
              scotthernandez 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
              scotthernandez 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
              Permalink
              scotthernandez Scott Hernandez added a comment -

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

              Show
              scotthernandez Scott Hernandez added a comment - Add counters about query planner (multiplan execution) and how often it is run on each collection/index.
              Hide
              Permalink
              scotthernandez 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
              scotthernandez 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
              Permalink
              scotthernandez 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
              scotthernandez 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
              Permalink
              pasette 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
              pasette 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
              Permalink
              kamaradclimber 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
              kamaradclimber 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:
                  11 Vote for this issue
                  Watchers:
                  23 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Days since reply:
                    3 years, 40 weeks, 4 days ago
                    Date of 1st Reply: