Ops Tools
441 results found
-
duplicate org creation
I am working on automation for creating organization using API. It allows to create multiple organization with same name. This should not be allowed.
1 vote -
Include Horizons as a replica set configuration option in the UI
Replica Set horizons cannot be set through the UI currently. It is possible to set through the automationConfig via the API but this is complex.
This would be useful for 2 use cases:
1. When a cluster is self-managed and using technologies like AWS PrivateLink
2. When a cluster is network isolated and connections must go through a proxy device1 vote -
Generate Security Reports in Ops Manager
- Create report about Mongo OPS users (ability to filter by Admin roles, Last Login, Created, Status)
- Create user report for All Mongo OPS Projects. Mongo DB Users (Filter by Organization, Project Name, MongoDB role, Auth database Synched/Not Synched)
1 vote -
mongocli ops-manager clusters reclaimFreeSpace [--help]
Explain this more than the current output
$ mongocli ops-manager clusters reclaimFreeSpace --help Reclaim unused space for a cluster. Usage: mongocli ops-manager clusters reclaimFreeSpace <clusterName> [flags]is of no use when customers want to know what this is doing, is this 'compact' or 'resync' equivalent? With some details, customers may be able to assess 'impact' of running this command.
1 vote -
Backup Resource Usage via Api
In Ops Manager, it is not possible to obtain some data from each snapshot via api, it is only available in ops manager interface. It is a good a idea to obtain from each snapshot the information of the backup resource usage. The api could return this information: "Store Type, Store Id Live, Compressed Bytes Dead, Compressed Bytes Compression Ratio, Last Groom, Last Track"
1 vote -
mongocli output text format not displaying all information
mongocli output text format not displaying all information where as json format dispalying all, if text can display same information as in Json. Will be helpful in updating the alerts etc.
1 vote -
EmptyDir as data-volume and log-volume
spec:
members: 1
type: ReplicaSet
version: "4.4.5"
statefulSet:
spec:
template:
spec:
volumes:
- name: data-volume
emptyDir: {}
- name: log-volume
emptyDir: {}This type of override would be very helpful for automated testing pipelines - pipeline should spin up single mongodb instance, populates data and proceed with application testing. For that, we don't need persistent volumes, we need clear folder on each invocation.
1 vote -
CRUD Operations history
We have many number of API/Micro service teams to consume the Mongodb for the data feeding. Sometimes, they ask the CRUD(Insert/Update/Delete queries , not the payload and actual data) history they performed in past. I don't see any option in mongodb how to retrieve those details?
1 vote -
Audit log gather from Ops manager
Do you have a plan to keep the option in future releases to gather audit log from Ops manager? I don't see any option now
1 vote -
Ops manager Apps DB logs archival policy in mongod.conf
I wanted to manage the Ops manager apps db logs in more refined by way by enabling "Size per Log Type in MB" and "Total Number of Files" settings in mongod.conf.
How ever I don't see any options "Size per Log Type in MB" and "Total Number of Files" but same avaiable in ops manager UI for agent managed replica set. Do you have a plan to add these options in mongod.conf in future releases for apps DB?1 vote -
disk iops
Can you please revert the change to metrics view for disk iops? It it completely unreadable and meaningless now.
There used to be 2 lines that made sense. Now there are 4... but looks like a bar chart. Anyway. Can't read it.
I would suggest.
1. have 1 view with 3 lines: 1 for the average read and 1 average write and 1 average BOTH.- have a second view showing the "burst" performance. Draw this as a LINE or scatter plot. Whatever you are drawing now is inscrutable.
thanks!
1 vote -
Ops Manager: more precise firewall configuration documentation
Currently, it is not clear from the documentation what are the source hosts for each port to open. The diagram fills in a bit this imprecision, but it is not formal enough. Also, some ports need to be open only if certain features are needed (eg. download link for snapshots).
This makes firewall configuration imprecise and experimental (or not as secure as it could be).
Suggestion: each table of the the Ops Manager firewall configuration webpage should document those columns:
- source component: client component(s)
- target component: server component(s)
- protocol: tcp/udp
- port
- feature: to specify if…1 vote -
Support Service Binding Specification for Kubernetes
Service Binding Specification for Kubernetes standardizes exposing backing service secrets to applications. The spec is available here: https://github.com/servicebinding/spec
This blog post would be helpful: https://muthukadan.net/kubernetes/binding/support-service-binding-specification-for-kubernetes/
1 voteLow customer demand. Potentially in the future if we hear sufficient demand.
-
Display the feature compatibility version (FCV) in Cloud Manager/Ops Manager UI
The FCV could be different than the MongoDB version. Also, sometime the FCV on different shards/CSRS in a sharded cluster might be different (e.g. FCV is upgraded on the shards, but for some reason FCV is not upgraded on the CSRS), and this could cause issues.
It would be nice if FCV is displayed next to the MongoDB version information. So that we can spot out the discrepancy quickly.
1 vote -
Enable S3 Snapshot Storage via Kubernetes Operator with IAM role
Configuring an S3 Snapshot Storage with IAM roles is only possible via Ops Manager UI or API.
It would be great to be able to do this configuration via the MongoDB Kubernetes Operator.
1 vote -
Allow Ops manager to downgrade FCV
Ops Manager UI (4.0 -4.4) does not allow downgrading of Feature Compatibility Version (FCV), once the FVC has been upgraded to a higher version. Ops Manager automatically
removes the lower version from the supported FCVs once upgrade completes. But the cluster deployment allows downgrading one level using shell commands. This limitation makes it difficult when planning an upgrade as regression process are more difficult.
We are in the process of upgrading the environment from 4.0 to 4.4 (which requires an intermediate upgrade to 4.2.). So the downgrade process is so difficult with Ops Manager UI.1 vote -
mongocli - allow to enable/disable agent modules
As of mongocli version 1.17.0 there is no way to enable monitoring and backup modules for a cloud manager or ops manager project.
You can only query the agents and the modules enabled.
This won't allow you to use mongocli to setup a new project from scratch and will require to use the Cloud Manager or Ops Manager API updating the automation config manually for this purpose.
1 vote -
Import existing MongoDB deployments
There should be a way to import existing MongoDB deployments with mongocli. This would allow the automated provisioning of Ops Manager instances in cases where MongoDB deployments already exist. In addition we would be able to import the application database of Ops Manager automatically whenever a new Ops Manager instance is installed.
1 vote -
Allow Ops Manager to only download specific MongoDB binary packages
We would like to have an option in the Ops Manager UI to select certain MongoDB versions to be automatically downloaded by Automation in order to avoid downloading all major binaries.
It is not good to have several MongoDB binaries using disk space and not being used.
1 vote -
Provide support to update version manifest to Ops Manager that uses local mode
With Ops Manager Local Mode on Kubernetes, the version manifest is required to be updated manually via UI or API.
It would be the best practice to support updating version manifest using a command to the Operator or OM Pods.
1 vote
- Don't see your idea?