Ops Tools

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  3. export & import alerts settings from one project to another project

    export & import alerts settings from one project to another project

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring / Alerts  ·  Flag idea as inappropriate…  ·  Admin →
  4. Provide AWS CloudFormation template starter

    It would make things easier for our users if they had at least a starter/example AWS CloudFormation template to use for provisioning AWS resources required for an Ops Manager deployment.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Automation  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  6. MongoDB kubernetes operator - follow recommended kubernetes object labeling -

    Hi, i would like to thank you first for this operator, good job 👍 . It works well.

    Did you consider using this label convention for objects (statefulset, svc, secrets) https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/?

    Currently in my cluster Im trying to follow these recommended labels for objects while Im forwarding kubernetes logs using EFK but cannot store log to elasticsearch because there is object mapping for kubernetes.labels.app field as object not a concrete value. Right now there is hard-coded service selector https://github.com/mongodb/mongodb-kubernetes-operator/blob/1aa7093d2cc977bc3b1f5a5fa7e1e902d37768c8/controllers/replica_set_controller.go#L455 which expects pods to be labeled with app=<serviceName>

    Example labels following conventions for statefulset:

    apiVersion: apps/v1
    kind: StatefulSet
    metadata:
      labels:
    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  10. k8s operator - Support different different size shard configuration

    We would like to implement the Hot-cold shard strategy to move the cold data to a shard which has more disk usage and less compute power and not frequently used and Hot data in a shard with more compute power. This strategy is described here: https://docs.mongodb.com/manual/tutorial/sharding-tiered-hardware-for-varying-slas/

    Currently the enterprise operator does not support different size shards, this request is to allow operator to create different size shards.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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.

    1. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring / Alerts  ·  Flag idea as inappropriate…  ·  Admin →
  12. Automation - Monitor ulimit parameters for mongo processes

    MongoDB will abort if ulimit parameters are set too low. We should monitor parameters such as "open files" and add an alert for when the value approaches the ulimit configuration.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  13. Dashboard in ops manager

    Can we have add dashboard feature in ops mgr which can give consolidated metrics of all RS.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  14. Trigger replica set alerts for hidden secondaries

    We need to ability to trigger replica set alerts when a secondary that is hidden goes down.

    In this example an environment has 4 members, with one of them "hidden". We would like to be alerted even when the "hidden" secondary goes down.

    Currently alerts are only working for non-hidden members.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  15. Allow multiple authentication sources simultaneously

    Currently Ops Manager authentication supports either the Application Database, LDAP, or SAML, but these methods cannot be combined. Ideally we would like to move to LDAP, but we are stuck with the local authentication method as we depend on a local admin user which is used when first deploying and configuring the Ops Manager ecosystem. We also do not want to depend solely on the availability of the LDAP servers regarding an admin user. The MongoDB cluster deployments do support multiple authentication methods at the same time (we have local admin and monitoring accounts while users are authenticating via LDAP),…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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/k8s-service-bindings/spec
    This blog post would be helpful: https://muthukadan.net/kubernetes/binding/support-service-binding-specification-for-kubernetes/

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
  18. Allow the use of symlinks within the Ops Manager directory

    Sometimes it would be great if we could move the conf, tmp, or logs directories to other filesystems and use symlinks so that Ops Manager doesn't have to worry about where the needed file physically are. Right now, Ops Manager refuses to start whenever this sort of redirection is done.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Ops Manager  ·  Flag idea as inappropriate…  ·  Admin →
  19. Incorrect Agent version Alert/Banner

    If someone upgrades from Ops Manager v4.2 -> v4.4 and then downgrades by reinstalling Ops Manager v4.2, there is no Alert or Banner that the Agent is incompatible.

    Attempts to modify deployments with this incompatible Agent displays "Initializing Automation for your Deployment" but never actually does anything. It is only after reviewing the Ops Manager logs that you see "Unrecognized field".

    It would be helpful if there was a validation check that displays an Alert or Banner that indicates that the version of the Agent is unknown/incompatible. Perhaps something similar to what is displayed after upgrading Ops Manager that will…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Automation  ·  Flag idea as inappropriate…  ·  Admin →
  20. Kubernetes Operator - Prefix Annotations and Labels

    Labels and annotations added to Kubernetes resources by the MongoDB Enterprise Operator should include a prefix designating that it was added by MongoDB. The lack of a prefix suggests the field and values are private to the user.

    For example, the MongoDB statefulset and service selector should use a label prefixed with a MongoDB domain.

    https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Kubernetes Operator  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 15 16
  • Don't see your idea?

Feedback and Knowledge Base