Page tree
Skip to end of metadata
Go to start of metadata
The full text of this page is only available to our customers.

Please login or sign up. You may also need to provide your support ID if you have not already done so.

Discover with BMC Discovery
download

This product can be discovered by Enterprise version of BMC Discovery, but you can still Download our free Community Edition to discover [other products] !

What is this?
This is a product information page, containing details of the information that BMC Discovery gathers about a product and how it is obtained.
Product Name
MongoDB
Publisher Page
MongoDB
Category
Nonrelational Database Management Systems
Release
TKU 2020-Jan-1
Change History
MongoDB MongoDB - Change History
Reports & Attributes
MongoDB MongoDB - Reports & Attributes
Publisher Link
MongoDB

Product Description

 

Extended Discovery pattern which models Database Detail Nodes being managed by the MongoDB Server  is available for this product.

 

The full text of this page is only available to our customers.

Please login or sign up. You may also need to provide your support ID if you have not already done so.

5 Comments

  1. MongoDB 2.6 and 3.0 have come out since this was last updated. Is there a plan for supporting the newer versions? In particular, 2.6 introduced a YAML-based configuration file which needs patterns.

  2. We plan to release an update that supports the latest versions in TKU November 

  3. Your triggers for MongoDB Server in this page don't match what you are shipping as part of the TKU.

    1. If you are referencing the regex us unix_cmd\windows_cmd part - they are basically the same.

      unix_cmd or windows_cmd just add \b and $ or (?i)\b and \.exe$ to the regexes.

      https://docs.bmc.com/docs/discovery/113/tpl-file-structure-788110511.html

      In the documentation you can see it written either with unix_cmd\windows_cmd or regex.


      1. We figured out why the MongoDB Server was not showing up although the trigger conditions were present.

        There is an issue in the pattern when the key is created and there is no other attributes are identified.

        Case Details:
        In the code, if the port, instance and db_path attributes are all blank/null, then the key will always be the same, which is what we’re seeing.

        The problem is that this code sets the key:
        key := 'MongoDB %si_type%';
        But then the bit that adds the host’s key to the end of the SI’s key is in the conditional code below, which in our case is never executed because those attributes are null/blank.
        For example:
        if port then
        key := "%port%/%key%/%host.key%";

        If set the initial key like this instead..
        key := 'MongoDB %si_type%/%host.key%';
        ..then there would be no problem (unless there were multiple DBs on one host, but at least in most cases it would be fine).

        I did this and the problem seems to have gone away

        key := 'MongoDBServer %si_type%/%host.key%';

        if port then
        key := "%port%/%key%";
        elif instance then
        key := "%instance%/%key%";

        Please feel free to create a better solution and share the love.