v1.82.0

Author: kishikawa12

docs/resources/browser_monitor.md

@@ -905,6 +905,11 @@ Required:
 - `creds` (String) A reference to the entry within the credential vault
 - `type` (String) The type of authentication
 
+Optional:
+
+- `auth_server_allowlist` (String) List of allowed servers, optional with Kerberos authentication
+- `domain` (String) User's domain name, required with Kerberos authentication
+
 
 <a id="nestedblock--script--events--event--navigate--target"></a>
 ### Nested Schema for `script.events.event.navigate.target`

docs/resources/log_agent_feature_flags.md

@@ -41,7 +41,7 @@ This setting enables:
 * Detection and collection of logs from short-lived containers and processes in Kubernetes.
 * Detection and collection of logs from any processes in containers in Kubernetes. Up until now only processes detected by OneAgent are covered with the Log module.
 * Log events decoration according to semantic dictionary.
- **Note:** The matcher "Deployment name" in the log sources configuration will be ignored and needs to be replaced with "Workload name", requires **Dynatrace Operator 1.4.1+**.
+ **Note:** The matcher "Deployment name" in the log sources configuration will be ignored and needs to be replaced with "Workload name", requires **Dynatrace Operator 1.4.2+**.
 
  For more details, check our [documentation](https://dt-url.net/jn02ey0).
 
@@ -51,6 +51,7 @@ This setting enables:
 This setting enables:
 * Detection and to have logs ingested matching ingest rule is required.
 - `scope` (String) The scope of this setting (HOST, KUBERNETES_CLUSTER, HOST_GROUP). Omit this property if you want to cover the whole environment.
+- `user_and_event_data` (Boolean) Enable OneAgent to collect data from Event Logs in the User Data and Event Data sections.
 
 ### Read-Only
 

docs/resources/openpipeline_business_events.md

@@ -108,6 +108,7 @@ Applicable processors are DqlProcessor, FieldsAddProcessor, FieldsRemoveProcesso
 Optional:
 
 - `dql_processor` (Block List, Max: 1) Processor to apply a DQL script (see [below for nested schema](#nestedblock--endpoints--endpoint--processors--processor--dql_processor))
+- `drop_processor` (Block List, Max: 1) Processor to drop the record either during the processing stage or at the endpoint (see [below for nested schema](#nestedblock--endpoints--endpoint--processors--processor--drop_processor))
 - `fields_add_processor` (Block List, Max: 1) Processor to add fields (see [below for nested schema](#nestedblock--endpoints--endpoint--processors--processor--fields_add_processor))
 - `fields_remove_processor` (Block List, Max: 1) Processor to remove fields (see [below for nested schema](#nestedblock--endpoints--endpoint--processors--processor--fields_remove_processor))
 - `fields_rename_processor` (Block List, Max: 1) Processor to rename fields (see [below for nested schema](#nestedblock--endpoints--endpoint--processors--processor--fields_rename_processor))
@@ -128,6 +129,21 @@ Optional:
 - `sample_data` (String) Sample data related to the processor for documentation or testing
 
 
+<a id="nestedblock--endpoints--endpoint--processors--processor--drop_processor"></a>
+### Nested Schema for `endpoints.endpoint.processors.processor.drop_processor`
+
+Required:
+
+- `description` (String) Name or description of the processor
+- `enabled` (Boolean) Indicates if the object is active
+- `id` (String) Identifier of the processor. Must be unique within a stage.
+- `matcher` (String) Matching condition to apply on incoming records
+
+Optional:
+
+- `sample_data` (String) Sample data related to the processor for documentation or testing
+
+
 <a id="nestedblock--endpoints--endpoint--processors--processor--fields_add_processor"></a>
 ### Nested Schema for `endpoints.endpoint.processors.processor.fields_add_processor`
 
@@ -252,7 +268,7 @@ Required:
 
 Optional:
 
-- `field_extraction` (Block List, Max: 1) (see [below for nested schema](#nestedblock--pipelines--pipeline--data_extraction--processor--bizevent_extraction_processor--field_extraction))
+- `field_extraction` (Block List, Max: 1) Definition of the field extraction (see [below for nested schema](#nestedblock--pipelines--pipeline--data_extraction--processor--bizevent_extraction_processor--field_extraction))
 - `sample_data` (String) Sample data related to the processor for documentation or testing
 
 <a id="nestedblock--pipelines--pipeline--data_extraction--processor--bizevent_extraction_processor--event_provider"></a>
@@ -286,8 +302,11 @@ Optional:
 
 Required:
 
-- `fields` (List of String)
-- `semantic` (String)
+- `semantic` (String) Defines how the fields of the source record should be extracted
+
+Optional:
+
+- `fields` (List of String) Unique fields to include/exclude in the extracted record
 
 
 
@@ -384,6 +403,7 @@ Applicable processors are DqlProcessor, FieldsAddProcessor, FieldsRemoveProcesso
 Optional:
 
 - `dql_processor` (Block List, Max: 1) Processor to apply a DQL script (see [below for nested schema](#nestedblock--pipelines--pipeline--processing--processor--dql_processor))
+- `drop_processor` (Block List, Max: 1) Processor to drop the record either during the processing stage or at the endpoint (see [below for nested schema](#nestedblock--pipelines--pipeline--processing--processor--drop_processor))
 - `fields_add_processor` (Block List, Max: 1) Processor to add fields (see [below for nested schema](#nestedblock--pipelines--pipeline--processing--processor--fields_add_processor))
 - `fields_remove_processor` (Block List, Max: 1) Processor to remove fields (see [below for nested schema](#nestedblock--pipelines--pipeline--processing--processor--fields_remove_processor))
 - `fields_rename_processor` (Block List, Max: 1) Processor to rename fields (see [below for nested schema](#nestedblock--pipelines--pipeline--processing--processor--fields_rename_processor))
@@ -405,6 +425,21 @@ Optional:
 - `sample_data` (String) Sample data related to the processor for documentation or testing
 
 
+<a id="nestedblock--pipelines--pipeline--processing--processor--drop_processor"></a>
+### Nested Schema for `pipelines.pipeline.processing.processor.drop_processor`
+
+Required:
+
+- `description` (String) Name or description of the processor
+- `enabled` (Boolean) Indicates if the object is active
+- `id` (String) Identifier of the processor. Must be unique within a stage.
+- `matcher` (String) Matching condition to apply on incoming records
+
+Optional:
+
+- `sample_data` (String) Sample data related to the processor for documentation or testing
+
+
 <a id="nestedblock--pipelines--pipeline--processing--processor--fields_add_processor"></a>
 ### Nested Schema for `pipelines.pipeline.processing.processor.fields_add_processor`
 

docs/resources/openpipeline_events.md

@@ -266,6 +266,7 @@ Applicable processors are DqlProcessor, FieldsAddProcessor, FieldsRemoveProcesso
 Optional:
 
 - `dql_processor` (Block List, Max: 1) Processor to apply a DQL script (see [below for nested schema](#nestedblock--endpoints--endpoint--processors--processor--dql_processor))
+- `drop_processor` (Block List, Max: 1) Processor to drop the record either during the processing stage or at the endpoint (see [below for nested schema](#nestedblock--endpoints--endpoint--processors--processor--drop_processor))
 - `fields_add_processor` (Block List, Max: 1) Processor to add fields (see [below for nested schema](#nestedblock--endpoints--endpoint--processors--processor--fields_add_processor))
 - `fields_remove_processor` (Block List, Max: 1) Processor to remove fields (see [below for nested schema](#nestedblock--endpoints--endpoint--processors--processor--fields_remove_processor))
 - `fields_rename_processor` (Block List, Max: 1) Processor to rename fields (see [below for nested schema](#nestedblock--endpoints--endpoint--processors--processor--fields_rename_processor))
@@ -286,6 +287,21 @@ Optional:
 - `sample_data` (String) Sample data related to the processor for documentation or testing
 
 
+<a id="nestedblock--endpoints--endpoint--processors--processor--drop_processor"></a>
+### Nested Schema for `endpoints.endpoint.processors.processor.drop_processor`
+
+Required:
+
+- `description` (String) Name or description of the processor
+- `enabled` (Boolean) Indicates if the object is active
+- `id` (String) Identifier of the processor. Must be unique within a stage.
+- `matcher` (String) Matching condition to apply on incoming records
+
+Optional:
+
+- `sample_data` (String) Sample data related to the processor for documentation or testing
+
+
 <a id="nestedblock--endpoints--endpoint--processors--processor--fields_add_processor"></a>
 ### Nested Schema for `endpoints.endpoint.processors.processor.fields_add_processor`
 
@@ -410,7 +426,7 @@ Required:
 
 Optional:
 
-- `field_extraction` (Block List, Max: 1) (see [below for nested schema](#nestedblock--pipelines--pipeline--data_extraction--processor--bizevent_extraction_processor--field_extraction))
+- `field_extraction` (Block List, Max: 1) Definition of the field extraction (see [below for nested schema](#nestedblock--pipelines--pipeline--data_extraction--processor--bizevent_extraction_processor--field_extraction))
 - `sample_data` (String) Sample data related to the processor for documentation or testing
 
 <a id="nestedblock--pipelines--pipeline--data_extraction--processor--bizevent_extraction_processor--event_provider"></a>
@@ -444,8 +460,11 @@ Optional:
 
 Required:
 
-- `fields` (List of String)
-- `semantic` (String)
+- `semantic` (String) Defines how the fields of the source record should be extracted
+
+Optional:
+
+- `fields` (List of String) Unique fields to include/exclude in the extracted record
 
 
 
@@ -542,6 +561,7 @@ Applicable processors are DqlProcessor, FieldsAddProcessor, FieldsRemoveProcesso
 Optional:
 
 - `dql_processor` (Block List, Max: 1) Processor to apply a DQL script (see [below for nested schema](#nestedblock--pipelines--pipeline--processing--processor--dql_processor))
+- `drop_processor` (Block List, Max: 1) Processor to drop the record either during the processing stage or at the endpoint (see [below for nested schema](#nestedblock--pipelines--pipeline--processing--processor--drop_processor))
 - `fields_add_processor` (Block List, Max: 1) Processor to add fields (see [below for nested schema](#nestedblock--pipelines--pipeline--processing--processor--fields_add_processor))
 - `fields_remove_processor` (Block List, Max: 1) Processor to remove fields (see [below for nested schema](#nestedblock--pipelines--pipeline--processing--processor--fields_remove_processor))
 - `fields_rename_processor` (Block List, Max: 1) Processor to rename fields (see [below for nested schema](#nestedblock--pipelines--pipeline--processing--processor--fields_rename_processor))
@@ -563,6 +583,21 @@ Optional:
 - `sample_data` (String) Sample data related to the processor for documentation or testing
 
 
+<a id="nestedblock--pipelines--pipeline--processing--processor--drop_processor"></a>
+### Nested Schema for `pipelines.pipeline.processing.processor.drop_processor`
+
+Required:
+
+- `description` (String) Name or description of the processor
+- `enabled` (Boolean) Indicates if the object is active
+- `id` (String) Identifier of the processor. Must be unique within a stage.
+- `matcher` (String) Matching condition to apply on incoming records
+
+Optional:
+
+- `sample_data` (String) Sample data related to the processor for documentation or testing
+
+
 <a id="nestedblock--pipelines--pipeline--processing--processor--fields_add_processor"></a>
 ### Nested Schema for `pipelines.pipeline.processing.processor.fields_add_processor`
 

docs/resources/openpipeline_logs.md

@@ -111,6 +111,7 @@ Applicable processors are DqlProcessor, FieldsAddProcessor, FieldsRemoveProcesso
 Optional:
 
 - `dql_processor` (Block List, Max: 1) Processor to apply a DQL script (see [below for nested schema](#nestedblock--endpoints--endpoint--processors--processor--dql_processor))
+- `drop_processor` (Block List, Max: 1) Processor to drop the record either during the processing stage or at the endpoint (see [below for nested schema](#nestedblock--endpoints--endpoint--processors--processor--drop_processor))
 - `fields_add_processor` (Block List, Max: 1) Processor to add fields (see [below for nested schema](#nestedblock--endpoints--endpoint--processors--processor--fields_add_processor))
 - `fields_remove_processor` (Block List, Max: 1) Processor to remove fields (see [below for nested schema](#nestedblock--endpoints--endpoint--processors--processor--fields_remove_processor))
 - `fields_rename_processor` (Block List, Max: 1) Processor to rename fields (see [below for nested schema](#nestedblock--endpoints--endpoint--processors--processor--fields_rename_processor))
@@ -131,6 +132,21 @@ Optional:
 - `sample_data` (String) Sample data related to the processor for documentation or testing
 
 
+<a id="nestedblock--endpoints--endpoint--processors--processor--drop_processor"></a>
+### Nested Schema for `endpoints.endpoint.processors.processor.drop_processor`
+
+Required:
+
+- `description` (String) Name or description of the processor
+- `enabled` (Boolean) Indicates if the object is active
+- `id` (String) Identifier of the processor. Must be unique within a stage.
+- `matcher` (String) Matching condition to apply on incoming records
+
+Optional:
+
+- `sample_data` (String) Sample data related to the processor for documentation or testing
+
+
 <a id="nestedblock--endpoints--endpoint--processors--processor--fields_add_processor"></a>
 ### Nested Schema for `endpoints.endpoint.processors.processor.fields_add_processor`
 
@@ -255,7 +271,7 @@ Required:
 
 Optional:
 
-- `field_extraction` (Block List, Max: 1) (see [below for nested schema](#nestedblock--pipelines--pipeline--data_extraction--processor--bizevent_extraction_processor--field_extraction))
+- `field_extraction` (Block List, Max: 1) Definition of the field extraction (see [below for nested schema](#nestedblock--pipelines--pipeline--data_extraction--processor--bizevent_extraction_processor--field_extraction))
 - `sample_data` (String) Sample data related to the processor for documentation or testing
 
 <a id="nestedblock--pipelines--pipeline--data_extraction--processor--bizevent_extraction_processor--event_provider"></a>
@@ -289,8 +305,11 @@ Optional:
 
 Required:
 
-- `fields` (List of String)
-- `semantic` (String)
+- `semantic` (String) Defines how the fields of the source record should be extracted
+
+Optional:
+
+- `fields` (List of String) Unique fields to include/exclude in the extracted record
 
 
 
@@ -387,6 +406,7 @@ Applicable processors are DqlProcessor, FieldsAddProcessor, FieldsRemoveProcesso
 Optional:
 
 - `dql_processor` (Block List, Max: 1) Processor to apply a DQL script (see [below for nested schema](#nestedblock--pipelines--pipeline--processing--processor--dql_processor))
+- `drop_processor` (Block List, Max: 1) Processor to drop the record either during the processing stage or at the endpoint (see [below for nested schema](#nestedblock--pipelines--pipeline--processing--processor--drop_processor))
 - `fields_add_processor` (Block List, Max: 1) Processor to add fields (see [below for nested schema](#nestedblock--pipelines--pipeline--processing--processor--fields_add_processor))
 - `fields_remove_processor` (Block List, Max: 1) Processor to remove fields (see [below for nested schema](#nestedblock--pipelines--pipeline--processing--processor--fields_remove_processor))
 - `fields_rename_processor` (Block List, Max: 1) Processor to rename fields (see [below for nested schema](#nestedblock--pipelines--pipeline--processing--processor--fields_rename_processor))
@@ -408,6 +428,21 @@ Optional:
 - `sample_data` (String) Sample data related to the processor for documentation or testing
 
 
+<a id="nestedblock--pipelines--pipeline--processing--processor--drop_processor"></a>
+### Nested Schema for `pipelines.pipeline.processing.processor.drop_processor`
+
+Required:
+
+- `description` (String) Name or description of the processor
+- `enabled` (Boolean) Indicates if the object is active
+- `id` (String) Identifier of the processor. Must be unique within a stage.
+- `matcher` (String) Matching condition to apply on incoming records
+
+Optional:
+
+- `sample_data` (String) Sample data related to the processor for documentation or testing
+
+
 <a id="nestedblock--pipelines--pipeline--processing--processor--fields_add_processor"></a>
 ### Nested Schema for `pipelines.pipeline.processing.processor.fields_add_processor`