Add config file details for alert configurations

Author: davidhou17

source/includes/alert-configuration-config-file.json

@@ -0,0 +1,26 @@
+{
+  "enabled": true,
+  "eventTypeName": "NO_PRIMARY",
+  "matchers": [
+    {
+      "fieldName": "REPLICA_SET_NAME",
+      "operator": "EQUALS",
+      "value": "event-replica-set"
+    }
+  ],
+  "notifications": [
+    {
+      "datadogApiKey": "****************************a23c",
+      "datadogRegion": "US",
+      "delayMin": 0,
+      "intervalMin": 5,
+      "notifierId": "6462742adc47d365036da07c",
+      "typeName": "DATADOG"
+    }
+  ],
+  "threshold": {
+    "operator": "<",
+    "threshold": 0,
+    "units": "bits"
+  }
+}

source/reference/json.txt

@@ -20,6 +20,8 @@ you can pass a configuration file when using the {+atlas-cli+} to:
 - :ref:`Create <atlas-clusters-search-indexes-create>` or 
   :ref:`update an Atlas Search Index <atlas-clusters-search-indexes-update>`.
 - :ref:`Create a {+df+} database <atlas-dataFederation-create>`.
+- :ref:`Create <atlas-alerts-settings-create>` or 
+  :ref:`update an alert configuration <atlas-alerts-settings-update>`.
 
 Usage
 -----
@@ -57,6 +59,12 @@ command. The commands you can use include but are not limited to:
   * - :ref:`atlas-dataFederation-create`
     - :oas-atlas-op:`Create One Federated Database Instance in One Project </createFederatedDatabase>`
 
+  * - :ref:`atlas-alerts-settings-create`
+    - :oas-atlas-op:`Create One Alert Configuration in One Project </createAlertConfiguration>`
+
+  * - :ref:`atlas-alerts-settings-update`
+    - :oas-atlas-op:`Update One Alert Configuration for One Project </updateAlertConfiguration>`
+
 When you run the command in your terminal, specify the ``--file`` option 
 and provide the path to the |json| configuration file that defines your 
 desired settings. 
@@ -120,10 +128,18 @@ To learn more about {+adf+} configuration files, see
 :ref:`atlas-cli-data-federation-config-file`. For a sample file,
 see :ref:`example-fdi-config-file`.
 
+Alert Configuration File
+------------------------
+
+To learn more about alert configuration files, see 
+:ref:`atlas-cli-alert-config-file`. For a sample file,
+see :ref:`example-alert-config-file`.
+
 .. toctree::
    :titlesonly:
 
    /reference/json/cluster-config-file
    /reference/json/cloud-backup-schedule-config-file
    /reference/json/data-federation-config-file
    /reference/json/search-index-config-file
+   /reference/json/alert-config-file

source/reference/json/alert-config-file.txt

@@ -0,0 +1,82 @@
+.. _atlas-cli-alert-config-file:
+
+========================
+Alert Configuration File
+========================
+
+.. contents:: On this page
+   :local:
+   :backlinks: none
+   :depth: 1
+   :class: singlecol
+
+You can use a configuration file to specify the
+settings for :ref:`creating <atlas-alerts-settings-create>`
+or :ref:`updating <atlas-alerts-settings-update>` an alert
+configuration through the {+atlas-cli+}. The {+atlas-cli+}
+accepts ``.json`` configuration files.
+
+.. _alert-config-settings:
+
+Alert Configuration Settings
+----------------------------
+
+Depending on the type of alert configuration, you can specify the 
+following settings to create or update an alert configuration 
+in a configuration file:
+
+.. list-table::
+   :widths: 20 10 70
+   :header-rows: 1
+
+   * - Field
+     - Type
+     - Description
+
+   * - ``enabled``
+     - boolean
+     - Flag that indicates whether someone enabled this
+       alert configuration for the specified project.
+
+   * - ``eventTypeName``
+     - string
+     - Required. Event type that triggers an alert.
+
+   * - ``matchers``
+     - array of objects
+     - Rules to apply when matching an object against this alert
+       configuration. You can use this field only if the ``eventTypeName``
+       specifies an event for a host, replica set, or sharded cluster.
+
+   * - ``metricThreshold``
+     - object
+     - Threshold for the metric that, when exceeded, triggers an alert.
+       You can use this field only if the ``eventTypeName`` reflects
+       a change in measurement or metric.
+
+   * - ``notifications``
+     - array of objects
+     - List that contains the targets that |service| sends notifications.
+
+   * - ``threshold``
+     - object
+     - A limit that triggers an alert when exceeded.
+
+For detailed descriptions and a full list of available settings,
+see the request body schema in the API specification:
+
+- :oas-atlas-op:`Create One Alert Configuration in One Project </createAlertConfiguration>`
+- :oas-atlas-op:`Update One Alert Configuration for One Project </updateAlertConfiguration>`
+
+.. _example-alert-config-file:
+
+Example Alert Configuration File
+--------------------------------
+
+To create or update an alert configuration, specify the
+fields that you want to include in the configuration file.
+For example, the following sample file enables an alert 
+configuration that notifies you when a replica set called 
+``event-replica-set`` loses its primary node:
+
+.. literalinclude:: /includes/alert-configuration-config-file.json