Ops Tools
448 results found
-
mongotop improvements
Hi. I want to suggest a couple of improvements for mongotop.
- count output in a grid view. Now only time is supported. Could be implemented with a command line flag
- limit the number of rows in a grid view with a command line flag (now 10 is hardcoded)
- pretty print of JSON (by flag)
- rename parameter rowcount to itercount
- date pretty print, something more human-readable than ISO format
- collect more granular stats from the top command. Now we only collect total and locks, * while we can insert, remove, update, etc.
I could implement them if the improvements are considered…
1 vote -
multi region support for MongoDB Community Operator
multi region support for MongoDB Community Operator
1 vote -
In Ops Mgr, provision to create users by deployment rather than by project
Under a project, Now if a user id created, it gets created in all deployments in the projects. Can we have provision to choose which deployment the user gets created.
For example, for project A, we have three deployments rs1, rs2 & rs3. Now under security tab, if we add a users, this user get access to all deployment. can we have a choice which all deployment the user exist.
3 votes -
More admin functionality for backup groom jobs
Currently it is possible to start a groom job, however once the groom is started no additional functionality is available. It would be convenient if a groom could be paused/stopped, if required, on the admin panel.
1 vote -
Restrict snapshot restore download
IHAC who would like to be able restrict snapshot restore download links (by IP / opsman role) to prevent anyone with access to opsman server from downloading. They know about the "number of times the restore link can be used" + "restore link expiration" features but would also like this feature. Please contact me for customer details
2 votes -
Do not trigger spurious COLLSCAN alerts for getmore commands during watch
Here's what MongoDB support summarizes about the current behavior: "Upon consulting with the team, they have confirmed that sometimes change streams can trigger collection scans, but these alerts are an artifact of how we calculate the metric today. Unfortunately at the moment, there is no fix for these alerts"
My suggestion is to fix how the metric is calculated. What is happening in the getmore is not a real COLLSCAN, and it should not be reported (and alerted) as such.
(Bonus points for including context information in the COLLSCAN threshold alert showing the collection and operation. Just knowing there has…
1 vote -
Mongoimport CSV columnsHaveTypes to support ObjectID type
Mongoimport supports a number of import types via the --columnsHaveTypes switch. It would be great if 'objectid' was added as a type.
1 vote -
mongoimport: trap SIGUSR1 to flush buffer
If mongoimport is run in the background as a daemon, the user doesn't have many good ways to manually flush the buffer from a scripting standpoint. By default mongoimport flushed data every 1000 documents.
This feature as already requested at https://jira.mongodb.org/browse/TOOLS-2773 but was closed. I still have the hope that it will be introduced somewhere in future release.
1 vote -
Migration Guide for OpsManager to enterprise-operator
It would be great to have a migration guide or documentation to help with migrating an existing OpsManager installation to the kubernetes enterprise-operator based installation.
2 votes -
Multiple webhook URLs
At the moment only one webhook URL can be configured for one Ops Manager project.
It would be nice if multiple URLs could be used to send the alert to different endpoints by using f.e. a delimiter character inside the config.
Thanks and regards3 votes -
On demand snapshots in Ops Manager
Allow the possibility of performing a snapshot on-demand.
Usually the snapshot time ends too far away in time after configuration changes of the backup job (i.e: changing the block size). For testing purposes it would make sense to allow performing a snapshot on-demand to get it generated and proceed with further testing/tuning if required.
80 votesWe have begun development to allow on demand snapshots in a future version of Ops Manger and Cloud Manager. I will provide an update at later time with a potential release date
-
Support Cloudian S3 in OpsManager
OpsManager currently supports the S3 implementations of AWS, IBM Cloud and Dell EMC Elastic Cloud Storage. We would like to use our existing Cloudian S3 storage. We've used it for a while now and it works, but we suggest making this an "officially supported" flavor, too.
1 vote -
Allow Regexp, or other solution, to look for groups in "SAML Group Member Attribute" field
The Ops Manager authentification process through SAML requires that the user's groups are specified in a dedicated SAML attribute sent by the IDP, so the user can connect to Ops Manager.
For this need, our IDP can only provide a field that contains free text. This field can contain many information, and can include special characters. We can add the Ops Manager groups in this field, among the existing text information.
However we need Ops Manager to parse this free field and get the groups information, which is not possible for now.
That's why we would like the implementation of…
4 votes -
Release Cadence to allow pegging Minor Version Upgrades prior to GA of next Major Release
Issue:
Current requirement to enable 'auto upgrades' to test and take advantage of Minor version updates (Example: 6.x.x >> 6.y.x). As a larger company with a 2-4 week release cycle in our products, we have seen need to start testing a Minor version upgrade to the current Major GA Release (Recent example below).Scenario where this could be a problem in summary (See detailed real world story further down):
- Customer sees a new feature they wish to try.
- Customer is pegged to last major version upgrade (currently 6.0.x) to allow for pegging the version in production
- Customer…1 vote -
MongoDB Tools Apple Silicon native version
6.0 now has a native release for Apple Silicon, but the tools are still compiled for x86_64. The https://github.com/mongodb/mongo-tools/blob/master/PLATFORMSUPPORT.md seems to point towards new platform support on internal systems like https://evergreen.mongodb.com/distros - can we get a native build of the tools ?
1 vote -
Add cluster_id parameter in host detail API
As per the link https://www.mongodb.com/docs/ops-manager/current/reference/api/measures/get-host-process-system-measurements/ and below API :
curl --user "{PUBLIC-KEY}:{PRIVATE-KEY}" --digest
--header "Accept: application/json"
--include
--request GET "https://{OPSMANAGER-HOST}:{PORT}/api/public/v1.0/groups/{PROJECT-ID}/hosts/{HOST-ID}/measurements?granularity={TIME-INCREMENT}&period={PERIOD}}&pretty=true"This will give us the details pertaining to one host and one project. However what if one host has multiple processes and part of multiple replica sets within same project in OPS Manager? Then it becomes difficult to gather gather data. Hence a clusterid parameter should also be added to distinguish details based on host pertaining to which cluster or replica set along with projectid which is already present.
1 vote -
Logging: attr.error field type conflicts
Hey!
We are using fluent-bit to push MongoDB logs to Elasticsearch. When there are already logs in the elastic index, where attr.error is an object, then it does not accept log lines in which this field is a string:
“error”:{“type”:“mapperparsingexception”,“reason”:“object mapping for [attr.error] tried to parse field [error] as object, but found a concrete value”}
There is log with string attr.error:
{“t”:{"$date":“2022-05-13T15:16:31.203+00:00”},“s”:“I”, “c”:“CONNPOOL”, “id”:22572, “ctx”:“MirrorMaestro”,“msg”:“Dropping all pooled connections”,“attr”:{“hostAndPort”:“mongodb-1.mongodb-headless.mongodb.svc.cluster.local:27017”,“error”:“ShutdownInProgress: Pool for mongodb-1.mongodb-headless.mongodb.svc.cluster.local:27017 has expired.”}}
There is log with object attr.error:
{“t”:{"$date":“2022-05-13T15:20:56.857+00:00”},“s”:“I”, “c”:“REPL_HB”, “id”:23974, “ctx”:“ReplCoord-680”,“msg”:“Heartbeat failed after max retries”,“attr”:{“target”:“alerta-mongodb-arbiter-0.alerta-mongodb-arbiter-headless.monitoring. svc.cluster.local:27017”,“maxHeartbeatRetries”:2,“error”:{“code”:93,“codeName”:“InvalidReplicaSetConfig”,“errmsg”:“replica set IDs do not match, ours: 61ea35f29cfd494fef169571; remote node’s: 61eef8589d065c56e61d6e52”}}}…
1 vote -
Rotate mongo logs
When cluster is deployed, each mongo server start to generate a logfile "/var/log/mongodb-mms-automation/mongodb.log", we got an outage because it gets the disk full.
It will be useful if we can specify a value to rotate and purge the log.4 votes -
Export Reports and Graphs
OPtions to export the reports and graphs into a PDF or office tool will help Incident Management process to a great extend.
1 vote -
rename action for backup daemon "delete daemon" to "deactivate daemon"
when you press link "delete daemon" on Admin->Backup->Daemons page it "deletes" daemon from this page, but after mongodb-mms.service gets restarted, this daemon comes up again. this link does not delete daemon - it actually deactivate backup daemon. another part for deactivation of daemon is to modify settings for service mongodb-mms to start only mms application without daemon.
1 vote
- Don't see your idea?