Dynatrace v0.16.0 published on Tuesday, Sep 10, 2024 by Pulumiverse
dynatrace.OpentelemetryMetrics
Explore with Pulumi AI
Create OpentelemetryMetrics Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new OpentelemetryMetrics(name: string, args?: OpentelemetryMetricsArgs, opts?: CustomResourceOptions);
@overload
def OpentelemetryMetrics(resource_name: str,
args: Optional[OpentelemetryMetricsArgs] = None,
opts: Optional[ResourceOptions] = None)
@overload
def OpentelemetryMetrics(resource_name: str,
opts: Optional[ResourceOptions] = None,
additional_attributes: Optional[OpentelemetryMetricsAdditionalAttributesArgs] = None,
additional_attributes_to_dimension_enabled: Optional[bool] = None,
meter_name_to_dimension_enabled: Optional[bool] = None,
mode: Optional[str] = None,
scope: Optional[str] = None,
to_drop_attributes: Optional[OpentelemetryMetricsToDropAttributesArgs] = None)
func NewOpentelemetryMetrics(ctx *Context, name string, args *OpentelemetryMetricsArgs, opts ...ResourceOption) (*OpentelemetryMetrics, error)
public OpentelemetryMetrics(string name, OpentelemetryMetricsArgs? args = null, CustomResourceOptions? opts = null)
public OpentelemetryMetrics(String name, OpentelemetryMetricsArgs args)
public OpentelemetryMetrics(String name, OpentelemetryMetricsArgs args, CustomResourceOptions options)
type: dynatrace:OpentelemetryMetrics
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args OpentelemetryMetricsArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args OpentelemetryMetricsArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args OpentelemetryMetricsArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args OpentelemetryMetricsArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args OpentelemetryMetricsArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
Constructor example
The following reference example uses placeholder values for all input properties.
var opentelemetryMetricsResource = new Dynatrace.OpentelemetryMetrics("opentelemetryMetricsResource", new()
{
AdditionalAttributes = new Dynatrace.Inputs.OpentelemetryMetricsAdditionalAttributesArgs
{
AdditionalAttributes = new[]
{
new Dynatrace.Inputs.OpentelemetryMetricsAdditionalAttributesAdditionalAttributeArgs
{
AttributeKey = "string",
Enabled = false,
},
},
},
AdditionalAttributesToDimensionEnabled = false,
MeterNameToDimensionEnabled = false,
Mode = "string",
Scope = "string",
ToDropAttributes = new Dynatrace.Inputs.OpentelemetryMetricsToDropAttributesArgs
{
ToDropAttributes = new[]
{
new Dynatrace.Inputs.OpentelemetryMetricsToDropAttributesToDropAttributeArgs
{
AttributeKey = "string",
Enabled = false,
},
},
},
});
example, err := dynatrace.NewOpentelemetryMetrics(ctx, "opentelemetryMetricsResource", &dynatrace.OpentelemetryMetricsArgs{
AdditionalAttributes: &dynatrace.OpentelemetryMetricsAdditionalAttributesArgs{
AdditionalAttributes: dynatrace.OpentelemetryMetricsAdditionalAttributesAdditionalAttributeArray{
&dynatrace.OpentelemetryMetricsAdditionalAttributesAdditionalAttributeArgs{
AttributeKey: pulumi.String("string"),
Enabled: pulumi.Bool(false),
},
},
},
AdditionalAttributesToDimensionEnabled: pulumi.Bool(false),
MeterNameToDimensionEnabled: pulumi.Bool(false),
Mode: pulumi.String("string"),
Scope: pulumi.String("string"),
ToDropAttributes: &dynatrace.OpentelemetryMetricsToDropAttributesArgs{
ToDropAttributes: dynatrace.OpentelemetryMetricsToDropAttributesToDropAttributeArray{
&dynatrace.OpentelemetryMetricsToDropAttributesToDropAttributeArgs{
AttributeKey: pulumi.String("string"),
Enabled: pulumi.Bool(false),
},
},
},
})
var opentelemetryMetricsResource = new OpentelemetryMetrics("opentelemetryMetricsResource", OpentelemetryMetricsArgs.builder()
.additionalAttributes(OpentelemetryMetricsAdditionalAttributesArgs.builder()
.additionalAttributes(OpentelemetryMetricsAdditionalAttributesAdditionalAttributeArgs.builder()
.attributeKey("string")
.enabled(false)
.build())
.build())
.additionalAttributesToDimensionEnabled(false)
.meterNameToDimensionEnabled(false)
.mode("string")
.scope("string")
.toDropAttributes(OpentelemetryMetricsToDropAttributesArgs.builder()
.toDropAttributes(OpentelemetryMetricsToDropAttributesToDropAttributeArgs.builder()
.attributeKey("string")
.enabled(false)
.build())
.build())
.build());
opentelemetry_metrics_resource = dynatrace.OpentelemetryMetrics("opentelemetryMetricsResource",
additional_attributes=dynatrace.OpentelemetryMetricsAdditionalAttributesArgs(
additional_attributes=[dynatrace.OpentelemetryMetricsAdditionalAttributesAdditionalAttributeArgs(
attribute_key="string",
enabled=False,
)],
),
additional_attributes_to_dimension_enabled=False,
meter_name_to_dimension_enabled=False,
mode="string",
scope="string",
to_drop_attributes=dynatrace.OpentelemetryMetricsToDropAttributesArgs(
to_drop_attributes=[dynatrace.OpentelemetryMetricsToDropAttributesToDropAttributeArgs(
attribute_key="string",
enabled=False,
)],
))
const opentelemetryMetricsResource = new dynatrace.OpentelemetryMetrics("opentelemetryMetricsResource", {
additionalAttributes: {
additionalAttributes: [{
attributeKey: "string",
enabled: false,
}],
},
additionalAttributesToDimensionEnabled: false,
meterNameToDimensionEnabled: false,
mode: "string",
scope: "string",
toDropAttributes: {
toDropAttributes: [{
attributeKey: "string",
enabled: false,
}],
},
});
type: dynatrace:OpentelemetryMetrics
properties:
additionalAttributes:
additionalAttributes:
- attributeKey: string
enabled: false
additionalAttributesToDimensionEnabled: false
meterNameToDimensionEnabled: false
mode: string
scope: string
toDropAttributes:
toDropAttributes:
- attributeKey: string
enabled: false
OpentelemetryMetrics Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
The OpentelemetryMetrics resource accepts the following input properties:
- Additional
Attributes Pulumiverse.Dynatrace. Inputs. Opentelemetry Metrics Additional Attributes - When enabled, the attributes defined in the list below will be added as dimensions to ingested OTLP metrics if they are present in the OpenTelemetry resource or in the instrumentation scope.
- Additional
Attributes boolTo Dimension Enabled - Add the resource and scope attributes configured below as dimensions
- Meter
Name boolTo Dimension Enabled - When enabled, the Meter name (also referred to as InstrumentationScope or InstrumentationLibrary in OpenTelemetry SDKs)
and version will be added as dimensions (
otel.scope.name
andotel.scope.version
) to ingested OTLP metrics. Note: Modifying this setting will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually - Mode string
- Scope string
- The scope of this setting (environment-default). Omit this property if you want to cover the whole environment.
- To
Drop Pulumiverse.Attributes Dynatrace. Inputs. Opentelemetry Metrics To Drop Attributes - The attributes defined in the list below will be dropped from all ingested OTLP metrics. Upon ingest, the Allow list: resource and scope attributes above is applied first. Then, the Deny list: all attributes below is applied. The deny list therefore applies to all attributes from all sources (data points, scope and resource). Notes: * Modifying this setting (adding, renaming, disabling or removing attributes) will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually. * Dynatrace does not recommend including attributes starting with "dt." to the deny list. Dynatrace leverages these attributes to Enrich metrics.
- Additional
Attributes OpentelemetryMetrics Additional Attributes Args - When enabled, the attributes defined in the list below will be added as dimensions to ingested OTLP metrics if they are present in the OpenTelemetry resource or in the instrumentation scope.
- Additional
Attributes boolTo Dimension Enabled - Add the resource and scope attributes configured below as dimensions
- Meter
Name boolTo Dimension Enabled - When enabled, the Meter name (also referred to as InstrumentationScope or InstrumentationLibrary in OpenTelemetry SDKs)
and version will be added as dimensions (
otel.scope.name
andotel.scope.version
) to ingested OTLP metrics. Note: Modifying this setting will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually - Mode string
- Scope string
- The scope of this setting (environment-default). Omit this property if you want to cover the whole environment.
- To
Drop OpentelemetryAttributes Metrics To Drop Attributes Args - The attributes defined in the list below will be dropped from all ingested OTLP metrics. Upon ingest, the Allow list: resource and scope attributes above is applied first. Then, the Deny list: all attributes below is applied. The deny list therefore applies to all attributes from all sources (data points, scope and resource). Notes: * Modifying this setting (adding, renaming, disabling or removing attributes) will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually. * Dynatrace does not recommend including attributes starting with "dt." to the deny list. Dynatrace leverages these attributes to Enrich metrics.
- additional
Attributes OpentelemetryMetrics Additional Attributes - When enabled, the attributes defined in the list below will be added as dimensions to ingested OTLP metrics if they are present in the OpenTelemetry resource or in the instrumentation scope.
- additional
Attributes BooleanTo Dimension Enabled - Add the resource and scope attributes configured below as dimensions
- meter
Name BooleanTo Dimension Enabled - When enabled, the Meter name (also referred to as InstrumentationScope or InstrumentationLibrary in OpenTelemetry SDKs)
and version will be added as dimensions (
otel.scope.name
andotel.scope.version
) to ingested OTLP metrics. Note: Modifying this setting will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually - mode String
- scope String
- The scope of this setting (environment-default). Omit this property if you want to cover the whole environment.
- to
Drop OpentelemetryAttributes Metrics To Drop Attributes - The attributes defined in the list below will be dropped from all ingested OTLP metrics. Upon ingest, the Allow list: resource and scope attributes above is applied first. Then, the Deny list: all attributes below is applied. The deny list therefore applies to all attributes from all sources (data points, scope and resource). Notes: * Modifying this setting (adding, renaming, disabling or removing attributes) will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually. * Dynatrace does not recommend including attributes starting with "dt." to the deny list. Dynatrace leverages these attributes to Enrich metrics.
- additional
Attributes OpentelemetryMetrics Additional Attributes - When enabled, the attributes defined in the list below will be added as dimensions to ingested OTLP metrics if they are present in the OpenTelemetry resource or in the instrumentation scope.
- additional
Attributes booleanTo Dimension Enabled - Add the resource and scope attributes configured below as dimensions
- meter
Name booleanTo Dimension Enabled - When enabled, the Meter name (also referred to as InstrumentationScope or InstrumentationLibrary in OpenTelemetry SDKs)
and version will be added as dimensions (
otel.scope.name
andotel.scope.version
) to ingested OTLP metrics. Note: Modifying this setting will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually - mode string
- scope string
- The scope of this setting (environment-default). Omit this property if you want to cover the whole environment.
- to
Drop OpentelemetryAttributes Metrics To Drop Attributes - The attributes defined in the list below will be dropped from all ingested OTLP metrics. Upon ingest, the Allow list: resource and scope attributes above is applied first. Then, the Deny list: all attributes below is applied. The deny list therefore applies to all attributes from all sources (data points, scope and resource). Notes: * Modifying this setting (adding, renaming, disabling or removing attributes) will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually. * Dynatrace does not recommend including attributes starting with "dt." to the deny list. Dynatrace leverages these attributes to Enrich metrics.
- additional_
attributes OpentelemetryMetrics Additional Attributes Args - When enabled, the attributes defined in the list below will be added as dimensions to ingested OTLP metrics if they are present in the OpenTelemetry resource or in the instrumentation scope.
- additional_
attributes_ boolto_ dimension_ enabled - Add the resource and scope attributes configured below as dimensions
- meter_
name_ boolto_ dimension_ enabled - When enabled, the Meter name (also referred to as InstrumentationScope or InstrumentationLibrary in OpenTelemetry SDKs)
and version will be added as dimensions (
otel.scope.name
andotel.scope.version
) to ingested OTLP metrics. Note: Modifying this setting will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually - mode str
- scope str
- The scope of this setting (environment-default). Omit this property if you want to cover the whole environment.
- to_
drop_ Opentelemetryattributes Metrics To Drop Attributes Args - The attributes defined in the list below will be dropped from all ingested OTLP metrics. Upon ingest, the Allow list: resource and scope attributes above is applied first. Then, the Deny list: all attributes below is applied. The deny list therefore applies to all attributes from all sources (data points, scope and resource). Notes: * Modifying this setting (adding, renaming, disabling or removing attributes) will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually. * Dynatrace does not recommend including attributes starting with "dt." to the deny list. Dynatrace leverages these attributes to Enrich metrics.
- additional
Attributes Property Map - When enabled, the attributes defined in the list below will be added as dimensions to ingested OTLP metrics if they are present in the OpenTelemetry resource or in the instrumentation scope.
- additional
Attributes BooleanTo Dimension Enabled - Add the resource and scope attributes configured below as dimensions
- meter
Name BooleanTo Dimension Enabled - When enabled, the Meter name (also referred to as InstrumentationScope or InstrumentationLibrary in OpenTelemetry SDKs)
and version will be added as dimensions (
otel.scope.name
andotel.scope.version
) to ingested OTLP metrics. Note: Modifying this setting will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually - mode String
- scope String
- The scope of this setting (environment-default). Omit this property if you want to cover the whole environment.
- to
Drop Property MapAttributes - The attributes defined in the list below will be dropped from all ingested OTLP metrics. Upon ingest, the Allow list: resource and scope attributes above is applied first. Then, the Deny list: all attributes below is applied. The deny list therefore applies to all attributes from all sources (data points, scope and resource). Notes: * Modifying this setting (adding, renaming, disabling or removing attributes) will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually. * Dynatrace does not recommend including attributes starting with "dt." to the deny list. Dynatrace leverages these attributes to Enrich metrics.
Outputs
All input properties are implicitly available as output properties. Additionally, the OpentelemetryMetrics resource produces the following output properties:
- Id string
- The provider-assigned unique ID for this managed resource.
- Id string
- The provider-assigned unique ID for this managed resource.
- id String
- The provider-assigned unique ID for this managed resource.
- id string
- The provider-assigned unique ID for this managed resource.
- id str
- The provider-assigned unique ID for this managed resource.
- id String
- The provider-assigned unique ID for this managed resource.
Look up Existing OpentelemetryMetrics Resource
Get an existing OpentelemetryMetrics resource’s state with the given name, ID, and optional extra properties used to qualify the lookup.
public static get(name: string, id: Input<ID>, state?: OpentelemetryMetricsState, opts?: CustomResourceOptions): OpentelemetryMetrics
@staticmethod
def get(resource_name: str,
id: str,
opts: Optional[ResourceOptions] = None,
additional_attributes: Optional[OpentelemetryMetricsAdditionalAttributesArgs] = None,
additional_attributes_to_dimension_enabled: Optional[bool] = None,
meter_name_to_dimension_enabled: Optional[bool] = None,
mode: Optional[str] = None,
scope: Optional[str] = None,
to_drop_attributes: Optional[OpentelemetryMetricsToDropAttributesArgs] = None) -> OpentelemetryMetrics
func GetOpentelemetryMetrics(ctx *Context, name string, id IDInput, state *OpentelemetryMetricsState, opts ...ResourceOption) (*OpentelemetryMetrics, error)
public static OpentelemetryMetrics Get(string name, Input<string> id, OpentelemetryMetricsState? state, CustomResourceOptions? opts = null)
public static OpentelemetryMetrics get(String name, Output<String> id, OpentelemetryMetricsState state, CustomResourceOptions options)
Resource lookup is not supported in YAML
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- resource_name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- name
- The unique name of the resulting resource.
- id
- The unique provider ID of the resource to lookup.
- state
- Any extra arguments used during the lookup.
- opts
- A bag of options that control this resource's behavior.
- Additional
Attributes Pulumiverse.Dynatrace. Inputs. Opentelemetry Metrics Additional Attributes - When enabled, the attributes defined in the list below will be added as dimensions to ingested OTLP metrics if they are present in the OpenTelemetry resource or in the instrumentation scope.
- Additional
Attributes boolTo Dimension Enabled - Add the resource and scope attributes configured below as dimensions
- Meter
Name boolTo Dimension Enabled - When enabled, the Meter name (also referred to as InstrumentationScope or InstrumentationLibrary in OpenTelemetry SDKs)
and version will be added as dimensions (
otel.scope.name
andotel.scope.version
) to ingested OTLP metrics. Note: Modifying this setting will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually - Mode string
- Scope string
- The scope of this setting (environment-default). Omit this property if you want to cover the whole environment.
- To
Drop Pulumiverse.Attributes Dynatrace. Inputs. Opentelemetry Metrics To Drop Attributes - The attributes defined in the list below will be dropped from all ingested OTLP metrics. Upon ingest, the Allow list: resource and scope attributes above is applied first. Then, the Deny list: all attributes below is applied. The deny list therefore applies to all attributes from all sources (data points, scope and resource). Notes: * Modifying this setting (adding, renaming, disabling or removing attributes) will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually. * Dynatrace does not recommend including attributes starting with "dt." to the deny list. Dynatrace leverages these attributes to Enrich metrics.
- Additional
Attributes OpentelemetryMetrics Additional Attributes Args - When enabled, the attributes defined in the list below will be added as dimensions to ingested OTLP metrics if they are present in the OpenTelemetry resource or in the instrumentation scope.
- Additional
Attributes boolTo Dimension Enabled - Add the resource and scope attributes configured below as dimensions
- Meter
Name boolTo Dimension Enabled - When enabled, the Meter name (also referred to as InstrumentationScope or InstrumentationLibrary in OpenTelemetry SDKs)
and version will be added as dimensions (
otel.scope.name
andotel.scope.version
) to ingested OTLP metrics. Note: Modifying this setting will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually - Mode string
- Scope string
- The scope of this setting (environment-default). Omit this property if you want to cover the whole environment.
- To
Drop OpentelemetryAttributes Metrics To Drop Attributes Args - The attributes defined in the list below will be dropped from all ingested OTLP metrics. Upon ingest, the Allow list: resource and scope attributes above is applied first. Then, the Deny list: all attributes below is applied. The deny list therefore applies to all attributes from all sources (data points, scope and resource). Notes: * Modifying this setting (adding, renaming, disabling or removing attributes) will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually. * Dynatrace does not recommend including attributes starting with "dt." to the deny list. Dynatrace leverages these attributes to Enrich metrics.
- additional
Attributes OpentelemetryMetrics Additional Attributes - When enabled, the attributes defined in the list below will be added as dimensions to ingested OTLP metrics if they are present in the OpenTelemetry resource or in the instrumentation scope.
- additional
Attributes BooleanTo Dimension Enabled - Add the resource and scope attributes configured below as dimensions
- meter
Name BooleanTo Dimension Enabled - When enabled, the Meter name (also referred to as InstrumentationScope or InstrumentationLibrary in OpenTelemetry SDKs)
and version will be added as dimensions (
otel.scope.name
andotel.scope.version
) to ingested OTLP metrics. Note: Modifying this setting will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually - mode String
- scope String
- The scope of this setting (environment-default). Omit this property if you want to cover the whole environment.
- to
Drop OpentelemetryAttributes Metrics To Drop Attributes - The attributes defined in the list below will be dropped from all ingested OTLP metrics. Upon ingest, the Allow list: resource and scope attributes above is applied first. Then, the Deny list: all attributes below is applied. The deny list therefore applies to all attributes from all sources (data points, scope and resource). Notes: * Modifying this setting (adding, renaming, disabling or removing attributes) will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually. * Dynatrace does not recommend including attributes starting with "dt." to the deny list. Dynatrace leverages these attributes to Enrich metrics.
- additional
Attributes OpentelemetryMetrics Additional Attributes - When enabled, the attributes defined in the list below will be added as dimensions to ingested OTLP metrics if they are present in the OpenTelemetry resource or in the instrumentation scope.
- additional
Attributes booleanTo Dimension Enabled - Add the resource and scope attributes configured below as dimensions
- meter
Name booleanTo Dimension Enabled - When enabled, the Meter name (also referred to as InstrumentationScope or InstrumentationLibrary in OpenTelemetry SDKs)
and version will be added as dimensions (
otel.scope.name
andotel.scope.version
) to ingested OTLP metrics. Note: Modifying this setting will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually - mode string
- scope string
- The scope of this setting (environment-default). Omit this property if you want to cover the whole environment.
- to
Drop OpentelemetryAttributes Metrics To Drop Attributes - The attributes defined in the list below will be dropped from all ingested OTLP metrics. Upon ingest, the Allow list: resource and scope attributes above is applied first. Then, the Deny list: all attributes below is applied. The deny list therefore applies to all attributes from all sources (data points, scope and resource). Notes: * Modifying this setting (adding, renaming, disabling or removing attributes) will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually. * Dynatrace does not recommend including attributes starting with "dt." to the deny list. Dynatrace leverages these attributes to Enrich metrics.
- additional_
attributes OpentelemetryMetrics Additional Attributes Args - When enabled, the attributes defined in the list below will be added as dimensions to ingested OTLP metrics if they are present in the OpenTelemetry resource or in the instrumentation scope.
- additional_
attributes_ boolto_ dimension_ enabled - Add the resource and scope attributes configured below as dimensions
- meter_
name_ boolto_ dimension_ enabled - When enabled, the Meter name (also referred to as InstrumentationScope or InstrumentationLibrary in OpenTelemetry SDKs)
and version will be added as dimensions (
otel.scope.name
andotel.scope.version
) to ingested OTLP metrics. Note: Modifying this setting will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually - mode str
- scope str
- The scope of this setting (environment-default). Omit this property if you want to cover the whole environment.
- to_
drop_ Opentelemetryattributes Metrics To Drop Attributes Args - The attributes defined in the list below will be dropped from all ingested OTLP metrics. Upon ingest, the Allow list: resource and scope attributes above is applied first. Then, the Deny list: all attributes below is applied. The deny list therefore applies to all attributes from all sources (data points, scope and resource). Notes: * Modifying this setting (adding, renaming, disabling or removing attributes) will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually. * Dynatrace does not recommend including attributes starting with "dt." to the deny list. Dynatrace leverages these attributes to Enrich metrics.
- additional
Attributes Property Map - When enabled, the attributes defined in the list below will be added as dimensions to ingested OTLP metrics if they are present in the OpenTelemetry resource or in the instrumentation scope.
- additional
Attributes BooleanTo Dimension Enabled - Add the resource and scope attributes configured below as dimensions
- meter
Name BooleanTo Dimension Enabled - When enabled, the Meter name (also referred to as InstrumentationScope or InstrumentationLibrary in OpenTelemetry SDKs)
and version will be added as dimensions (
otel.scope.name
andotel.scope.version
) to ingested OTLP metrics. Note: Modifying this setting will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually - mode String
- scope String
- The scope of this setting (environment-default). Omit this property if you want to cover the whole environment.
- to
Drop Property MapAttributes - The attributes defined in the list below will be dropped from all ingested OTLP metrics. Upon ingest, the Allow list: resource and scope attributes above is applied first. Then, the Deny list: all attributes below is applied. The deny list therefore applies to all attributes from all sources (data points, scope and resource). Notes: * Modifying this setting (adding, renaming, disabling or removing attributes) will cause the metric to change. This may have an impact on existing dashboards, events and alerts that make use of these dimensions. In this case, they will need to be updated manually. * Dynatrace does not recommend including attributes starting with "dt." to the deny list. Dynatrace leverages these attributes to Enrich metrics.
Supporting Types
OpentelemetryMetricsAdditionalAttributes, OpentelemetryMetricsAdditionalAttributesArgs
OpentelemetryMetricsAdditionalAttributesAdditionalAttribute, OpentelemetryMetricsAdditionalAttributesAdditionalAttributeArgs
- Attribute
Key string - Attribute key
- Enabled bool
- This setting is enabled (
true
) or disabled (false
)
- Attribute
Key string - Attribute key
- Enabled bool
- This setting is enabled (
true
) or disabled (false
)
- attribute
Key String - Attribute key
- enabled Boolean
- This setting is enabled (
true
) or disabled (false
)
- attribute
Key string - Attribute key
- enabled boolean
- This setting is enabled (
true
) or disabled (false
)
- attribute_
key str - Attribute key
- enabled bool
- This setting is enabled (
true
) or disabled (false
)
- attribute
Key String - Attribute key
- enabled Boolean
- This setting is enabled (
true
) or disabled (false
)
OpentelemetryMetricsToDropAttributes, OpentelemetryMetricsToDropAttributesArgs
OpentelemetryMetricsToDropAttributesToDropAttribute, OpentelemetryMetricsToDropAttributesToDropAttributeArgs
- Attribute
Key string - Attribute key
- Enabled bool
- This setting is enabled (
true
) or disabled (false
)
- Attribute
Key string - Attribute key
- Enabled bool
- This setting is enabled (
true
) or disabled (false
)
- attribute
Key String - Attribute key
- enabled Boolean
- This setting is enabled (
true
) or disabled (false
)
- attribute
Key string - Attribute key
- enabled boolean
- This setting is enabled (
true
) or disabled (false
)
- attribute_
key str - Attribute key
- enabled bool
- This setting is enabled (
true
) or disabled (false
)
- attribute
Key String - Attribute key
- enabled Boolean
- This setting is enabled (
true
) or disabled (false
)
Package Details
- Repository
- dynatrace pulumiverse/pulumi-dynatrace
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
dynatrace
Terraform Provider.