incorporated more comments

Author: ashwinkumar12345

docs/ad/api.md

@@ -249,7 +249,7 @@ POST _opendistro/_anomaly_detection/detectors
   "description": "test historical detector",
   "time_field": "timestamp",
   "indices": [
-    "nab_art_daily_jumpsdown"
+    "host-cloudwatch"
   ],
   "filter_query": {
     "match_all": {
@@ -775,7 +775,16 @@ POST _opendistro/_anomaly_detection/detectors/results/_search
 }
 ```
 
-In historical detectors, specify the `detector_id`:
+In historical detectors, specify the `detector_id`.
+To get the latest task:
+
+#### Request
+
+```json
+GET _opendistro/_anomaly_detection/detectors/<detector_id>?task=true
+```
+
+To query the anomaly results with `task_id`:
 
 #### Request
 
@@ -784,8 +793,8 @@ GET _opendistro/_anomaly_detection/detectors/results/_search
 {
   "query": {
     "term": {
-      "detector_id": {
-        "value": "dZc8WncBgO2zoQoFWVBA"
+      "task_id": {
+        "value": "NnlV9HUBQxqfQ7vBJNzy"
       }
     }
   }
@@ -925,7 +934,7 @@ GET _opendistro/_anomaly_detection/detectors/results/_search
 ## Delete detector
 
 Deletes a detector based on the `detector_id`.
-To delete a historical detector, you need to first stop the detector.
+To delete a detector, you need to first stop the detector.
 
 #### Request
 
@@ -959,7 +968,8 @@ DELETE _opendistro/_anomaly_detection/detectors/<detectorId>
 
 ## Update detector
 
-Updates a detector with any changes, including the description or adding or removing of features. You can't update a real-time detector to a historical detector or vice versa.
+Updates a detector with any changes, including the description or adding or removing of features.
+To update a detector, you need to first stop the detector.
 
 #### Request
 
@@ -1075,7 +1085,7 @@ PUT _opendistro/_anomaly_detection/detectors/<detectorId>
 }
 ```
 
-To update a historical detector, you need to first stop the detector.
+To update a historical detector:
 
 #### Request
 

docs/ad/settings.md

@@ -36,7 +36,7 @@ Setting | Default | Description
 `opendistro.anomaly_detection.max_primary_shards` | 10 | The maximum number of primary shards an anomaly detection index can have.
 `opendistro.anomaly_detection.filter_by_backend_roles` | False | When you enable the security plugin and set this to `true`, the plugin filters results based on the user's backend role(s).
 `opendistro.anomaly_detection.max_cache_miss_handling_per_second` | 100 | High cardinality detectors use a cache to store active models. In the event of a cache miss, the cache gets the models from the model checkpoint index. Use this setting to limit the rate of fetching models. Because the thread pool for a GET operation has a queue of 1,000, we recommend setting this value below 1,000.
-`opendistro.anomaly_detection.max_batch_task_per_node` | 2 | Starting a historical detector triggers a batch task. This setting is the number of batch tasks that you can run per data node. You can tune this setting from 1 to 1000. If the data nodes can't support all batch tasks, add more data nodes instead of changing this setting to a higher value.
+`opendistro.anomaly_detection.max_batch_task_per_node` | 2 | Starting a historical detector triggers a batch task. This setting is the number of batch tasks that you can run per data node. You can tune this setting from 1 to 1000. If the data nodes can't support all batch tasks and if you're not sure if the data nodes are capable of running more historical detectors, add more data nodes instead of changing this setting to a higher value.
 `opendistro.anomaly_detection.max_old_ad_task_docs_per_detector` | 10 | You can run the same historical detector many times. For each run, the anomaly detection plugin creates a new task. This setting is the number of previous tasks the plugin keeps. Set this value to at least 1 to track its last run. You can keep a maximum of 1,000 old tasks to avoid overwhelming the cluster.
 `opendistro.anomaly_detection.batch_task_piece_size` | 1000 | The date range for a historical task is split into smaller pieces and the anomaly detection plugin runs the task piece by piece. Each piece contains 1,000 detection intervals by default. For example, if detector interval is 1 minute and one piece is 1000 minutes, the feature data is queried every 1,000 minutes. You can change this setting from 1 to 10,000.
 `opendistro.anomaly_detection.batch_task_piece_interval_seconds` | 5 | Add a time interval between historical detector tasks. This interval prevents the task from consuming too much of the available resources and starving other operations like search and bulk index. You can change this setting from 1 to 600 seconds.