Ops Tools
467 results found
-
Atlas Open Service Broker - Roles
Is it possible to add the support for user roles to the bind api for the Atlas Open Service Broker?
Customers that are currently using the OSB are limited in that they are having to separately manage the creation and assignment of roles.
2 votes -
we have certain instances where we have more than one databases for their own respective functionality. and we want to keep their backups se
we have certain instances where we have more than one databases for their own respective functionality. and we want to keep their backups separate from each other. would separate or individual backup/restore process is available through Ops Manager?
2 votes -
Ops Mgr "Insufficient oplog size" is confusing and prevents backups
When using Ops Manager UI (I've not checked the API) to declare a MongoDB cluster to be backed up, Ops Manager tries to be a good citizen and check to see if the clusters oplogs are large enough, based on their recent usage to hold at least 3 hours worth of data based on the last 24 hours of usage patterns. if the check fails, the user is prevented from enabling backup and is shown the warning:
"Insufficient oplog size: The oplog window must be at least 3 hours over the last 24 hours for all members of replica set…
2 votes -
Allow to configure separate SNMP v2C community for SNMP v2C Heartbeat Traps and SNMP v2C Alert Traps
What is the problem that needs to be solved? Allow to configure separate SNMP v2C community for SNMP v2C Heartbeat Traps and SNMP v2C Alert Traps.
Why is it a problem? (the pain) As of now (2020-03-24) there's no way to configure separate SNMP v2C community for SNMP v2C Heartbeat Traps and SNMP v2C Alert Traps (
snmp.communitycontrols both, Heartbeat and Alert Traps sent from Ops Manager's Application Server), some SNMP Monitoring Teams require different SNMP v2C communities for different set of SNMP v2C Traps (to separate Heartbeat Traps and Alert Traps).2 votes -
Allow Point-In-Time restores going back to a configured amount of hours/days
What is the problem that needs to be solved? Allow Point-In-Time restores going back to a configured amount of hours/days (similar to Ops Manager).
Why is it a problem? (the pain) Oplogs are captured for the last 24 hours only, and sometimes the requirement is to be able to execute Point-In-Time restores for longer than 24 hours (48 hours, etc. (to be defined by customer's project/goal)).
2 votes -
Allow honorSystemUmask to be set on Ops Manager HEADDBs
If honorSystemUmask is set to false, new files created by MongoDB have permissions set to 600, which gives read and write permissions only to the owner. New directories have permissions set to 700.
As a result it makes it difficult to read the HEADDB logs in some environments. Allowing honorSystemUmask to be configurable would allow the customer to choose permissions based on their own security policies.
2 votes -
Group Host Mapping IPs to be added by default to Programmatic API Keys IP Whitelisting
As part of the Programmatic API Keys introduced in MongoDB Ops Manager 4.2, it would be good to have the IPs listed in the Host Mappings of a Project Deployment to be added as default whitelisted IPs when setting up a Programmatic API Key for same Project.
2 votes -
Add configuration option to disable seedSecondary scripts in snapshots
Currently each snapshot includes the seedSecondary scripts that no longer work for MongoDB 3.6 or greater.
-r-x-w-r-t 1 107 65534 767 Jan 30 11:40 seedSecondary.sh -rw-r--r-- 1 107 65534 754 Jan 30 11:40 seedSecondary.batPlease add an option to disable adding these files to snapshots or remove them completely as they are deprecated for MongoDB 3.6+.
2 votes -
2 votes
-
For Mongosync add ability to select write concern.
For Mongosync add ability to select write concern. Especially something along the "all" nodes would be important. Also "custom" one like MultipleDC etc.
1 vote -
Automatically move HEADS in case of backup daemon problem
In configuration with multiply daemons in case of daemon problem (down) switch to another one automatically with restart backup upon need.
1 vote -
Warn when trying to apply changes that are doomed to fail
Ops Manager UI should show a warning when trying to publish changes while a node is disabled (shut down).
Why ? See this example:
- user publishes a change asking for node 1 to be disabled
- publication is OK, node 1 is stopped by Ops Manager
- user publishes a change asking for node 2 to restart. Ops Manager UI accepts this change...
- ...but publication will fail, with node 2 agent waiting indefinitely for node 1 to get healthyThis is really disturbing because Ops Manger accepts a change it knows it can't deliver.
1 vote -
Different networks support in Ops Manager
We need Ops Manager being able to manage our infrastructure architecture.
We have a service network and an operational network. The servers, at the physical level, are located in the operational network with their domain (for example servername.operational.network.net, which is what is in /etc/hosts and what you get when you run "hostname -f") and the replica set nodes, at the MongoDB level, are in the service network (for example servername.service.network.net).
When you try to add an existing MongoDB deployment in Ops Manager, as indicated in the wizard, you must do it with the name…
1 vote -
Operator opsManager.configMapRef as a secret
currently inside the mongodb Operator custom resource
MongoDB, a configMap stores the orgId.
e.g.
apiVersion: mongodb.com/v1
kind: MongoDB
metadata:
name: my-mongodb
spec:
...
opsManager:
configMapRef:
name: my-mongodb-ops-manager-diga-project-configmap
credentials: my-mongodb-opsmanager
please allow storing the orgID inside a secret via:
spec:
...
opsManager:
secretRef:
name: my-mongodb-ops-manager-diga-project-secret
credentials: my-mongodb-opsmanager
1 vote -
Add support in homebrew for mongosync
Could you add support in https://github.com/mongodb/homebrew-brew for mongosync https://www.mongodb.com/try/download/mongosync
1 vote -
Allow OPS Manager to export as CSV or JSON All projects page information
All projects page in MongoOPS shows cluster name, data size, version, nodes, backup, SSL, Auth, Alerts.
Add export as CSV or JSON All projects page information.
Current MongoDB Usage report doesn't fit due:
1. It doesn't report backup, encryption information
2. Cluster name could be not right if the cluster was unmanaged and added back to OPS manager as managed. (Cluster_0 bogus names)1 vote -
The Backup Daemon auto downloads all old Mongodb versions
If "Backup Versions Auto Download" is set to true on the Admin > General > Ops Manager Config > MISCELLANEOUS tab, then the backup daemon automatically downloads all older major versions of the software.
In my opinion, it would be better if you could either select the version/s which you want or it only downloaded versions equal to or higher than your current version.
All the old versions take up disk space and can only be deleted if the setting is changed to false.
thanks1 vote -
Mongo Atlas: create backup before updating version
If I upgrade Atlas cluster, Atlas automatically creates a backup with the new version.
I'd rather have a backup of the cluster with original version.
It will allow to restore to the previous version.
Current workaround: create a backup manually before upgrade.1 vote -
encryption at rest
Right now there is only option to encrypt the key used to encrypt the database. There is no way we can choose which encryption technology is being used to encrypting the database and its backups. The default protocol being used by mongodb may not align with the security policy of the company.
1 vote -
1 vote
- Don't see your idea?