Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-34230

Implement setFreeMonitoring command and actionTypes

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.7.6
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Platforms 2018-04-23

      {setFreeMonitoring : 1, action: (enable | disable) }

      Parameters:
      action: enable|disable - see description before
      Returns:
      ok: bool - true if the command was successful, false otherwise
      This command can only be run on primaries.
      It requires the user to have action setFreeMonitoring to run. This action is part of the clusterManager role.
      If the state changes from disabled to enabled, or from enabled to enabled the server will register itself with Cloud. A registration call will occur regardless of whether the server already attempted registration or was previously registered.
      Only one setFreeMonitoring can proceed at a time. The command behaves as if there is a global lock coordinate all callers of the command.
      If the state changes from enabled to disabled, the server will stop uploading metrics.
      If the state changes from disabled to disabled, the server will do nothing
      If registration succeeds, it returns

      { ok: 1 }

      .
      If registration fails, it returns

      { ok: 0, errmsg ... }

      If registration times out, it returns

      { ok: 0, errmsg : timeout }

            Assignee:
            sara.golemon@mongodb.com Sara Golemon
            Reporter:
            greg.mckeon@mongodb.com Gregory McKeon (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: