add mon_extended.

aws/documentation/naming-tagging-standard/tags/mon.md

@@ -11,10 +11,11 @@ They are prefixed with a label of `mon_`.
 
 The following tags are to be applied to resources which support tagging.
 
-| Tag key               | Status   |
-|-----------------------|----------|
-| mon_priority | Required |
-| mon_visibility | Required |
+| Tag key               | Status   | Notes |
+|-----------------------|----------|-------|
+| mon_priority | Required | |
+| mon_visibility | Required | |
+| mon_extended | Optional | Applies to ec2, lambda |
 
 # Applicability
 
@@ -74,9 +75,34 @@ The tag name is all lowercase, and *must* be set to `mon_visibility`.
 | external | This resource is externally available, but not open to the public as a whole |
 | internal | This is an internal only resource | 
 
+## mon_extended
+
+This was formerly `mon_enabled`.  We have changed it because of confusion on what is meant by the tag use within Datadog.
+
+This is `OPTIONAL` for resources of type EC2 or Lammbda.  It is a way to enable monitor data caputuring by Datadog _only_.  Every 
+AWS account integration with Datadog will *not* consume additional logging licenses for EC2 and Lambda.  To obtain the additional
+monitoring of EC2 and Lambda, one must add this tag `mon_extended=true` to the resource (EC2, Lambda).
+
+### Format
+
+The tag name is all lowercase, and *must* be set to `mon_extended`.
+
+### Values
+
+Datadog only cares about `mon_extended=true`.  Any other value means _false_. Oomiting the tag is the better way of indicating
+this additional monitoring is not enabled.  
+
+| Value | Description |
+|-------|-------------|
+| true | This enables collection of additional metrics by Datadog from EC2 and Lambda only |
+| false | No additional monitoring from metrics for Datadog for EC2 and Lambda |
+| (anything else) | Equivalent to _false_ |
+
 # CHANGELOG
 
 - 1.0.0 -- 2024-10-16  
   - initial  
 - 1.0.1 -- 2024-10-23  
   - add tags  
+- 1.0.2 -- 2025-01-08
+  - add mon_extended