Ops Manager Profiler
Parent: Database Profiler vs Query Profiler · Published reference · snapshot 2026-10-23 · skill mongodb-cohort-9767e9fb3174
↓ Facts as markdownall context files
Source-anchored research for Ops Manager Profiler. Run status: COMPLETED.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
Structure and components
- The documented display stops at the first of 10,000 recent operations or 10 MB of logs; charts contain at most 10,000 points. Batching can delay results by five minutes. (low confidence) (verified as of 2026-10-14) [source]
How it works
- For an empty Profiler, check whether the agent can read mongod log files. In an April 2024 incident, root-owned process logs were inaccessible to the mongodb agent user; restarting mongod under mongodb restored data. (medium confidence) [source]
How-to and procedures
- Use the Profiler to inspect operation statistics, then use Performance Advisor for index recommendations; visualization and index advice are separate tools. (high confidence) [source]
Measurements and reference values
- The documented display cap is the first reached of 10,000 recent operations or 10 MB of logs; batch processing can delay data by five minutes. (low confidence) (verified as of 2026-10-14) [source]
- Kinekube’s August 18, 2026 Ops Manager walkthrough separately configures operationProfiling.mode: slowOp and slowOpThresholdMs: 100 in additionalMongodConfig. This is evidence of database-profiler configuration in an Ops Manager deployment, not proof the Ops Manager Profiler requires that configuration. (medium confidence) [source]
Problems, failure modes and limitations
- Ops Manager Profiler tails mongod slow-query logs; it does not write system.profile. Its project collection switch does not enable or disable the database profiler. (medium confidence) [source]
- Ops Manager 4.4.0, released July 8, 2020, changed the default Profiler data source to slow-query logs. Its release notes also describe a historical Profiler Nds flag to revert to profiler entries; that flag is not evidence of current support. (medium confidence) [source]
- The feature requires MongoDB Agent with Automation. The documented default slow threshold is 100 ms per mongod; profiling has been enabled by default since Ops Manager 4.4. (low confidence) (verified as of 2026-10-14) [source]
- Ops Manager presents a sample of historical slow operations for up to 24 hours; its bounded Profiler display should not be treated as a complete audit of every database operation. (medium confidence) (verified as of 2026-10-14) [source]
- The current tutorial documents a default 100 ms slow-operation threshold and default Profiler enablement since version 4.4; the project settings documentation confirms the threshold belongs to the mongod instance. (medium confidence) (verified as of 2026-10-14) [source]
Comparisons and alternatives
- Ops Manager Profiler visualizes slow operations by tailing mongod diagnostic logs. It is a management interface over log evidence, rather than the database profiler that records operations in system.profile. (high confidence) [source]
Facts and statements
- The Profiler offers charts and tables filtered by time, namespace, operation type, and metrics such as execution time, keys examined, and examined-to-returned ratio. (low confidence) [source]
- The Performance Advisor and Profiler project setting controls log tailing and access to both pages. Query content can expose sensitive data. (medium confidence) [source]
- IBM documents query profiling and automated index recommendations among the Ops Manager monitoring features of its MongoDB Enterprise plan; this is deployment-context evidence, not independent verification of the collection implementation. (low confidence) (verified as of 2026-10-23) [source]
- The project-level Performance Advisor and Profiler switch controls log collection and both pages for all project users; it does not enable or disable the database profiler on mongod. (high confidence) [source]
- The documented Ops Manager Profiler requires MongoDB Agent with Automation. (low confidence) (verified as of 2026-10-14) [source]
- Query text and personally identifiable information may appear in profiling data, so granting access to the Ops Manager interface can expose sensitive workload information. (high confidence) [source]
- For an empty Profiler page, check whether the agent can read mongod logs. An April 2024 operator report traced missing data to logs owned by root that the mongodb agent user could not access; this is a reported incident, not a universal diagnosis. (medium confidence) [source]
- A database profiling level of zero does not by itself prove Ops Manager Profiler is disabled: project log collection and database profiling are separate controls. The 2024 incident reported working Profiler pages despite level zero. (high confidence) [source]
- Independent coverage has limited relevance: Datadog’s 2016 guide describes Ops Manager as a monitoring tool, while Kinekube’s August 2026 walkthrough configures database operationProfiling. Neither independently verifies the current Ops Manager Profiler ingestion pipeline. (medium confidence) [source]
Children
- No children recorded.