Docs Home Pulumi IaC Pulumi ESC Pulumi Cloud Packages Tutorials
  1. Packages
  2. Dynatrace
  3. API Docs
  4. DataPrivacy
Dynatrace v0.16.0 published on Tuesday, Sep 10, 2024 by Pulumiverse
pulumiverse/pulumi-dynatrace

dynatrace.DataPrivacy

Explore with Pulumi AI

dynatrace logo
Dynatrace v0.16.0 published on Tuesday, Sep 10, 2024 by Pulumiverse
pulumiverse/pulumi-dynatrace

    Create DataPrivacy Resource

    Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.

    Constructor syntax

    new DataPrivacy(name: string, args: DataPrivacyArgs, opts?: CustomResourceOptions);
    @overload
def DataPrivacy(resource_name: str,
                args: DataPrivacyArgs,
                opts: Optional[ResourceOptions] = None)

@overload
def DataPrivacy(resource_name: str,
                opts: Optional[ResourceOptions] = None,
                data_collection: Optional[DataPrivacyDataCollectionArgs] = None,
                do_not_track: Optional[DataPrivacyDoNotTrackArgs] = None,
                masking: Optional[DataPrivacyMaskingArgs] = None,
                user_tracking: Optional[DataPrivacyUserTrackingArgs] = None,
                application_id: Optional[str] = None)
    func NewDataPrivacy(ctx *Context, name string, args DataPrivacyArgs, opts ...ResourceOption) (*DataPrivacy, error)
    public DataPrivacy(string name, DataPrivacyArgs args, CustomResourceOptions? opts = null)
    public DataPrivacy(String name, DataPrivacyArgs args)
public DataPrivacy(String name, DataPrivacyArgs args, CustomResourceOptions options)

    type: dynatrace:DataPrivacy
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 DataPrivacyArgs
    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 DataPrivacyArgs
    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 DataPrivacyArgs
    The arguments to resource properties.
    opts ResourceOption
    Bag of options to control resource's behavior.
    name string
    The unique name of the resource.
    args DataPrivacyArgs
    The arguments to resource properties.
    opts CustomResourceOptions
    Bag of options to control resource's behavior.
    name String
    The unique name of the resource.
    args DataPrivacyArgs
    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 dataPrivacyResource = new Dynatrace.DataPrivacy("dataPrivacyResource", new()
{
    DataCollection = new Dynatrace.Inputs.DataPrivacyDataCollectionArgs
    {
        OptInModeEnabled = false,
    },
    DoNotTrack = new Dynatrace.Inputs.DataPrivacyDoNotTrackArgs
    {
        ComplyWithDoNotTrack = false,
        DoNotTrack = "string",
    },
    Masking = new Dynatrace.Inputs.DataPrivacyMaskingArgs
    {
        PersonalDataUriMaskingEnabled = false,
        UserActionMaskingEnabled = false,
    },
    UserTracking = new Dynatrace.Inputs.DataPrivacyUserTrackingArgs
    {
        PersistentCookieEnabled = false,
    },
    ApplicationId = "string",
});

    example, err := dynatrace.NewDataPrivacy(ctx, "dataPrivacyResource", &dynatrace.DataPrivacyArgs{
	DataCollection: &dynatrace.DataPrivacyDataCollectionArgs{
		OptInModeEnabled: pulumi.Bool(false),
	},
	DoNotTrack: &dynatrace.DataPrivacyDoNotTrackArgs{
		ComplyWithDoNotTrack: pulumi.Bool(false),
		DoNotTrack:           pulumi.String("string"),
	},
	Masking: &dynatrace.DataPrivacyMaskingArgs{
		PersonalDataUriMaskingEnabled: pulumi.Bool(false),
		UserActionMaskingEnabled:      pulumi.Bool(false),
	},
	UserTracking: &dynatrace.DataPrivacyUserTrackingArgs{
		PersistentCookieEnabled: pulumi.Bool(false),
	},
	ApplicationId: pulumi.String("string"),
})

    var dataPrivacyResource = new DataPrivacy("dataPrivacyResource", DataPrivacyArgs.builder()
    .dataCollection(DataPrivacyDataCollectionArgs.builder()
        .optInModeEnabled(false)
        .build())
    .doNotTrack(DataPrivacyDoNotTrackArgs.builder()
        .complyWithDoNotTrack(false)
        .doNotTrack("string")
        .build())
    .masking(DataPrivacyMaskingArgs.builder()
        .personalDataUriMaskingEnabled(false)
        .userActionMaskingEnabled(false)
        .build())
    .userTracking(DataPrivacyUserTrackingArgs.builder()
        .persistentCookieEnabled(false)
        .build())
    .applicationId("string")
    .build());

    data_privacy_resource = dynatrace.DataPrivacy("dataPrivacyResource",
    data_collection=dynatrace.DataPrivacyDataCollectionArgs(
        opt_in_mode_enabled=False,
    ),
    do_not_track=dynatrace.DataPrivacyDoNotTrackArgs(
        comply_with_do_not_track=False,
        do_not_track="string",
    ),
    masking=dynatrace.DataPrivacyMaskingArgs(
        personal_data_uri_masking_enabled=False,
        user_action_masking_enabled=False,
    ),
    user_tracking=dynatrace.DataPrivacyUserTrackingArgs(
        persistent_cookie_enabled=False,
    ),
    application_id="string")

    const dataPrivacyResource = new dynatrace.DataPrivacy("dataPrivacyResource", {
    dataCollection: {
        optInModeEnabled: false,
    },
    doNotTrack: {
        complyWithDoNotTrack: false,
        doNotTrack: "string",
    },
    masking: {
        personalDataUriMaskingEnabled: false,
        userActionMaskingEnabled: false,
    },
    userTracking: {
        persistentCookieEnabled: false,
    },
    applicationId: "string",
});

    type: dynatrace:DataPrivacy
properties:
    applicationId: string
    dataCollection:
        optInModeEnabled: false
    doNotTrack:
        complyWithDoNotTrack: false
        doNotTrack: string
    masking:
        personalDataUriMaskingEnabled: false
        userActionMaskingEnabled: false
    userTracking:
        persistentCookieEnabled: false

    DataPrivacy 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 DataPrivacy resource accepts the following input properties:

    DataCollection Pulumiverse.Dynatrace.Inputs.DataPrivacyDataCollection
    To provide your end users with the ability to decide for themselves if their activities should be tracked to measure application performance and usage, enable opt-in mode.
    DoNotTrack Pulumiverse.Dynatrace.Inputs.DataPrivacyDoNotTrack
    Most modern web browsers have a privacy feature called "Do Not Track" that individual users may have enabled on their devices. Customize how Dynatrace should behave when it encounters this setting.
    Masking Pulumiverse.Dynatrace.Inputs.DataPrivacyMasking
    no documentation available
    UserTracking Pulumiverse.Dynatrace.Inputs.DataPrivacyUserTracking
    User tracking
    ApplicationId string
    The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
    DataCollection DataPrivacyDataCollectionArgs
    To provide your end users with the ability to decide for themselves if their activities should be tracked to measure application performance and usage, enable opt-in mode.
    DoNotTrack DataPrivacyDoNotTrackArgs
    Most modern web browsers have a privacy feature called "Do Not Track" that individual users may have enabled on their devices. Customize how Dynatrace should behave when it encounters this setting.
    Masking DataPrivacyMaskingArgs
    no documentation available
    UserTracking DataPrivacyUserTrackingArgs
    User tracking
    ApplicationId string
    The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
    dataCollection DataPrivacyDataCollection
    To provide your end users with the ability to decide for themselves if their activities should be tracked to measure application performance and usage, enable opt-in mode.
    doNotTrack DataPrivacyDoNotTrack
    Most modern web browsers have a privacy feature called "Do Not Track" that individual users may have enabled on their devices. Customize how Dynatrace should behave when it encounters this setting.
    masking DataPrivacyMasking
    no documentation available
    userTracking DataPrivacyUserTracking
    User tracking
    applicationId String
    The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
    dataCollection DataPrivacyDataCollection
    To provide your end users with the ability to decide for themselves if their activities should be tracked to measure application performance and usage, enable opt-in mode.
    doNotTrack DataPrivacyDoNotTrack
    Most modern web browsers have a privacy feature called "Do Not Track" that individual users may have enabled on their devices. Customize how Dynatrace should behave when it encounters this setting.
    masking DataPrivacyMasking
    no documentation available
    userTracking DataPrivacyUserTracking
    User tracking
    applicationId string
    The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
    data_collection DataPrivacyDataCollectionArgs
    To provide your end users with the ability to decide for themselves if their activities should be tracked to measure application performance and usage, enable opt-in mode.
    do_not_track DataPrivacyDoNotTrackArgs
    Most modern web browsers have a privacy feature called "Do Not Track" that individual users may have enabled on their devices. Customize how Dynatrace should behave when it encounters this setting.
    masking DataPrivacyMaskingArgs
    no documentation available
    user_tracking DataPrivacyUserTrackingArgs
    User tracking
    application_id str
    The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
    dataCollection Property Map
    To provide your end users with the ability to decide for themselves if their activities should be tracked to measure application performance and usage, enable opt-in mode.
    doNotTrack Property Map
    Most modern web browsers have a privacy feature called "Do Not Track" that individual users may have enabled on their devices. Customize how Dynatrace should behave when it encounters this setting.
    masking Property Map
    no documentation available
    userTracking Property Map
    User tracking
    applicationId String
    The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.

    Outputs

    All input properties are implicitly available as output properties. Additionally, the DataPrivacy 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 DataPrivacy Resource

    Get an existing DataPrivacy 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?: DataPrivacyState, opts?: CustomResourceOptions): DataPrivacy
    @staticmethod
def get(resource_name: str,
        id: str,
        opts: Optional[ResourceOptions] = None,
        application_id: Optional[str] = None,
        data_collection: Optional[DataPrivacyDataCollectionArgs] = None,
        do_not_track: Optional[DataPrivacyDoNotTrackArgs] = None,
        masking: Optional[DataPrivacyMaskingArgs] = None,
        user_tracking: Optional[DataPrivacyUserTrackingArgs] = None) -> DataPrivacy
    func GetDataPrivacy(ctx *Context, name string, id IDInput, state *DataPrivacyState, opts ...ResourceOption) (*DataPrivacy, error)
    public static DataPrivacy Get(string name, Input<string> id, DataPrivacyState? state, CustomResourceOptions? opts = null)
    public static DataPrivacy get(String name, Output<String> id, DataPrivacyState 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.
    The following state arguments are supported:
    ApplicationId string
    The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
    DataCollection Pulumiverse.Dynatrace.Inputs.DataPrivacyDataCollection
    To provide your end users with the ability to decide for themselves if their activities should be tracked to measure application performance and usage, enable opt-in mode.
    DoNotTrack Pulumiverse.Dynatrace.Inputs.DataPrivacyDoNotTrack
    Most modern web browsers have a privacy feature called "Do Not Track" that individual users may have enabled on their devices. Customize how Dynatrace should behave when it encounters this setting.
    Masking Pulumiverse.Dynatrace.Inputs.DataPrivacyMasking
    no documentation available
    UserTracking Pulumiverse.Dynatrace.Inputs.DataPrivacyUserTracking
    User tracking
    ApplicationId string
    The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
    DataCollection DataPrivacyDataCollectionArgs
    To provide your end users with the ability to decide for themselves if their activities should be tracked to measure application performance and usage, enable opt-in mode.
    DoNotTrack DataPrivacyDoNotTrackArgs
    Most modern web browsers have a privacy feature called "Do Not Track" that individual users may have enabled on their devices. Customize how Dynatrace should behave when it encounters this setting.
    Masking DataPrivacyMaskingArgs
    no documentation available
    UserTracking DataPrivacyUserTrackingArgs
    User tracking
    applicationId String
    The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
    dataCollection DataPrivacyDataCollection
    To provide your end users with the ability to decide for themselves if their activities should be tracked to measure application performance and usage, enable opt-in mode.
    doNotTrack DataPrivacyDoNotTrack
    Most modern web browsers have a privacy feature called "Do Not Track" that individual users may have enabled on their devices. Customize how Dynatrace should behave when it encounters this setting.
    masking DataPrivacyMasking
    no documentation available
    userTracking DataPrivacyUserTracking
    User tracking
    applicationId string
    The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
    dataCollection DataPrivacyDataCollection
    To provide your end users with the ability to decide for themselves if their activities should be tracked to measure application performance and usage, enable opt-in mode.
    doNotTrack DataPrivacyDoNotTrack
    Most modern web browsers have a privacy feature called "Do Not Track" that individual users may have enabled on their devices. Customize how Dynatrace should behave when it encounters this setting.
    masking DataPrivacyMasking
    no documentation available
    userTracking DataPrivacyUserTracking
    User tracking
    application_id str
    The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
    data_collection DataPrivacyDataCollectionArgs
    To provide your end users with the ability to decide for themselves if their activities should be tracked to measure application performance and usage, enable opt-in mode.
    do_not_track DataPrivacyDoNotTrackArgs
    Most modern web browsers have a privacy feature called "Do Not Track" that individual users may have enabled on their devices. Customize how Dynatrace should behave when it encounters this setting.
    masking DataPrivacyMaskingArgs
    no documentation available
    user_tracking DataPrivacyUserTrackingArgs
    User tracking
    applicationId String
    The scope of this settings. If the settings should cover the whole environment, just don't specify any scope.
    dataCollection Property Map
    To provide your end users with the ability to decide for themselves if their activities should be tracked to measure application performance and usage, enable opt-in mode.
    doNotTrack Property Map
    Most modern web browsers have a privacy feature called "Do Not Track" that individual users may have enabled on their devices. Customize how Dynatrace should behave when it encounters this setting.
    masking Property Map
    no documentation available
    userTracking Property Map
    User tracking

    Supporting Types

    DataPrivacyDataCollection, DataPrivacyDataCollectionArgs

    OptInModeEnabled bool
    With Data-collection and opt-in mode enabled, Real User Monitoring data isn't captured until dtrum.enable() is called for specific user sessions.
    OptInModeEnabled bool
    With Data-collection and opt-in mode enabled, Real User Monitoring data isn't captured until dtrum.enable() is called for specific user sessions.
    optInModeEnabled Boolean
    With Data-collection and opt-in mode enabled, Real User Monitoring data isn't captured until dtrum.enable() is called for specific user sessions.
    optInModeEnabled boolean
    With Data-collection and opt-in mode enabled, Real User Monitoring data isn't captured until dtrum.enable() is called for specific user sessions.
    opt_in_mode_enabled bool
    With Data-collection and opt-in mode enabled, Real User Monitoring data isn't captured until dtrum.enable() is called for specific user sessions.
    optInModeEnabled Boolean
    With Data-collection and opt-in mode enabled, Real User Monitoring data isn't captured until dtrum.enable() is called for specific user sessions.

    DataPrivacyDoNotTrack, DataPrivacyDoNotTrackArgs

    ComplyWithDoNotTrack bool
    Comply with "Do Not Track" browser settings
    DoNotTrack string
    Possible Values: Anonymous, Disable_rum
    ComplyWithDoNotTrack bool
    Comply with "Do Not Track" browser settings
    DoNotTrack string
    Possible Values: Anonymous, Disable_rum
    complyWithDoNotTrack Boolean
    Comply with "Do Not Track" browser settings
    doNotTrack String
    Possible Values: Anonymous, Disable_rum
    complyWithDoNotTrack boolean
    Comply with "Do Not Track" browser settings
    doNotTrack string
    Possible Values: Anonymous, Disable_rum
    comply_with_do_not_track bool
    Comply with "Do Not Track" browser settings
    do_not_track str
    Possible Values: Anonymous, Disable_rum
    complyWithDoNotTrack Boolean
    Comply with "Do Not Track" browser settings
    doNotTrack String
    Possible Values: Anonymous, Disable_rum

    DataPrivacyMasking, DataPrivacyMaskingArgs

    PersonalDataUriMaskingEnabled bool
    Dynatrace captures the URIs and request headers sent from desktop and mobile browsers. Dynatrace also captures full URIs on the server-side to enable detailed performance analysis of your applications. For complete details, visit Mask personal data in URIs.. URIs and request headers contain personal data. When this setting is enabled, Dynatrace automatically detects UUIDs, credit card numbers, email addresses, IP addresses, and other IDs and replaces those values with placeholders. The personal data is then masked in PurePath analysis, error analysis, user action naming for RUM, and elsewhere in Dynatrace.
    UserActionMaskingEnabled bool

    When Dynatrace detects a user action that triggers a page load or an AJAX/XHR action. To learn more about masking user actions, visit Mask user actions.. When Dynatrace detects a user action that triggers a page load or an AJAX/XHR action, it constructs a name for the user action based on:

    • User event type (click on..., loading of page..., or keypress on...)
    • Title, caption, label, value, ID, className, or other available property of the related HTML element (for example, an image, button, checkbox, or text input field).

    In most instances, the default approach to user-action naming works well, resulting in user-action names such as:

    • click on "Search" on page /search.html
    • keypress on "Feedback" on page /contact.html
    • touch on "Homescreen" of page /list.jsf

    In rare circumstances, confidential data (for example, email addresses, usernames, or account numbers) can be unintentionally included in user action names because the confidential data itself is included in an HTML element label, attribute, or other value (for example, click on "my Account Number: 1231231"...). If such confidential data appears in your application's user action names, enable the Mask user action names setting. This setting replaces specific HTML element names and values with generic HTML element names. With user-action name masking enabled, the user action names listed above appear as:

    • click on INPUT on page /search.html
    • keypress on TEXTAREA on page /contact.html
    • touch on DIV of page /list.jsf
    IpAddressMasking string
    Possible Values: All, Public

    Deprecated: This property is not supported anymore by the Dynatrace REST API (since schema version 4)

    IpAddressMaskingEnabled bool

    Dynatrace captures the IP addresses of your end-users to determine the regions from which they access your application. To learn more, visit Mask IPs and GPS coordinates.. Dynatrace also captures GPS data from mobile apps that provide their users with the option of sharing geolocation data. On the server side, Dynatrace captures IP addresses to enable detailed troubleshooting for Dynatrace service calls.

    Once enabled, IP address masking sets the last octet of monitored IPv4 addresses and the last 80 bits of IPv6 addresses to zeroes. GPS coordinates are rounded up to 1 decimal place (~10 km). This masking occurs in memory. Full IP addresses are never written to disk. Location lookups are made using anonymized IP addresses and GPS coordinates.

    Deprecated: This property is not supported anymore by the Dynatrace REST API (since schema version 4)

    PersonalDataUriMaskingEnabled bool
    Dynatrace captures the URIs and request headers sent from desktop and mobile browsers. Dynatrace also captures full URIs on the server-side to enable detailed performance analysis of your applications. For complete details, visit Mask personal data in URIs.. URIs and request headers contain personal data. When this setting is enabled, Dynatrace automatically detects UUIDs, credit card numbers, email addresses, IP addresses, and other IDs and replaces those values with placeholders. The personal data is then masked in PurePath analysis, error analysis, user action naming for RUM, and elsewhere in Dynatrace.
    UserActionMaskingEnabled bool

    When Dynatrace detects a user action that triggers a page load or an AJAX/XHR action. To learn more about masking user actions, visit Mask user actions.. When Dynatrace detects a user action that triggers a page load or an AJAX/XHR action, it constructs a name for the user action based on:

    • User event type (click on..., loading of page..., or keypress on...)
    • Title, caption, label, value, ID, className, or other available property of the related HTML element (for example, an image, button, checkbox, or text input field).

    In most instances, the default approach to user-action naming works well, resulting in user-action names such as:

    • click on "Search" on page /search.html
    • keypress on "Feedback" on page /contact.html
    • touch on "Homescreen" of page /list.jsf

    In rare circumstances, confidential data (for example, email addresses, usernames, or account numbers) can be unintentionally included in user action names because the confidential data itself is included in an HTML element label, attribute, or other value (for example, click on "my Account Number: 1231231"...). If such confidential data appears in your application's user action names, enable the Mask user action names setting. This setting replaces specific HTML element names and values with generic HTML element names. With user-action name masking enabled, the user action names listed above appear as:

    • click on INPUT on page /search.html
    • keypress on TEXTAREA on page /contact.html
    • touch on DIV of page /list.jsf
    IpAddressMasking string
    Possible Values: All, Public

    Deprecated: This property is not supported anymore by the Dynatrace REST API (since schema version 4)

    IpAddressMaskingEnabled bool

    Dynatrace captures the IP addresses of your end-users to determine the regions from which they access your application. To learn more, visit Mask IPs and GPS coordinates.. Dynatrace also captures GPS data from mobile apps that provide their users with the option of sharing geolocation data. On the server side, Dynatrace captures IP addresses to enable detailed troubleshooting for Dynatrace service calls.

    Once enabled, IP address masking sets the last octet of monitored IPv4 addresses and the last 80 bits of IPv6 addresses to zeroes. GPS coordinates are rounded up to 1 decimal place (~10 km). This masking occurs in memory. Full IP addresses are never written to disk. Location lookups are made using anonymized IP addresses and GPS coordinates.

    Deprecated: This property is not supported anymore by the Dynatrace REST API (since schema version 4)

    personalDataUriMaskingEnabled Boolean
    Dynatrace captures the URIs and request headers sent from desktop and mobile browsers. Dynatrace also captures full URIs on the server-side to enable detailed performance analysis of your applications. For complete details, visit Mask personal data in URIs.. URIs and request headers contain personal data. When this setting is enabled, Dynatrace automatically detects UUIDs, credit card numbers, email addresses, IP addresses, and other IDs and replaces those values with placeholders. The personal data is then masked in PurePath analysis, error analysis, user action naming for RUM, and elsewhere in Dynatrace.
    userActionMaskingEnabled Boolean

    When Dynatrace detects a user action that triggers a page load or an AJAX/XHR action. To learn more about masking user actions, visit Mask user actions.. When Dynatrace detects a user action that triggers a page load or an AJAX/XHR action, it constructs a name for the user action based on:

    • User event type (click on..., loading of page..., or keypress on...)
    • Title, caption, label, value, ID, className, or other available property of the related HTML element (for example, an image, button, checkbox, or text input field).

    In most instances, the default approach to user-action naming works well, resulting in user-action names such as:

    • click on "Search" on page /search.html
    • keypress on "Feedback" on page /contact.html
    • touch on "Homescreen" of page /list.jsf

    In rare circumstances, confidential data (for example, email addresses, usernames, or account numbers) can be unintentionally included in user action names because the confidential data itself is included in an HTML element label, attribute, or other value (for example, click on "my Account Number: 1231231"...). If such confidential data appears in your application's user action names, enable the Mask user action names setting. This setting replaces specific HTML element names and values with generic HTML element names. With user-action name masking enabled, the user action names listed above appear as:

    • click on INPUT on page /search.html
    • keypress on TEXTAREA on page /contact.html
    • touch on DIV of page /list.jsf
    ipAddressMasking String
    Possible Values: All, Public

    Deprecated: This property is not supported anymore by the Dynatrace REST API (since schema version 4)

    ipAddressMaskingEnabled Boolean

    Dynatrace captures the IP addresses of your end-users to determine the regions from which they access your application. To learn more, visit Mask IPs and GPS coordinates.. Dynatrace also captures GPS data from mobile apps that provide their users with the option of sharing geolocation data. On the server side, Dynatrace captures IP addresses to enable detailed troubleshooting for Dynatrace service calls.

    Once enabled, IP address masking sets the last octet of monitored IPv4 addresses and the last 80 bits of IPv6 addresses to zeroes. GPS coordinates are rounded up to 1 decimal place (~10 km). This masking occurs in memory. Full IP addresses are never written to disk. Location lookups are made using anonymized IP addresses and GPS coordinates.

    Deprecated: This property is not supported anymore by the Dynatrace REST API (since schema version 4)

    personalDataUriMaskingEnabled boolean
    Dynatrace captures the URIs and request headers sent from desktop and mobile browsers. Dynatrace also captures full URIs on the server-side to enable detailed performance analysis of your applications. For complete details, visit Mask personal data in URIs.. URIs and request headers contain personal data. When this setting is enabled, Dynatrace automatically detects UUIDs, credit card numbers, email addresses, IP addresses, and other IDs and replaces those values with placeholders. The personal data is then masked in PurePath analysis, error analysis, user action naming for RUM, and elsewhere in Dynatrace.
    userActionMaskingEnabled boolean

    When Dynatrace detects a user action that triggers a page load or an AJAX/XHR action. To learn more about masking user actions, visit Mask user actions.. When Dynatrace detects a user action that triggers a page load or an AJAX/XHR action, it constructs a name for the user action based on:

    • User event type (click on..., loading of page..., or keypress on...)
    • Title, caption, label, value, ID, className, or other available property of the related HTML element (for example, an image, button, checkbox, or text input field).

    In most instances, the default approach to user-action naming works well, resulting in user-action names such as:

    • click on "Search" on page /search.html
    • keypress on "Feedback" on page /contact.html
    • touch on "Homescreen" of page /list.jsf

    In rare circumstances, confidential data (for example, email addresses, usernames, or account numbers) can be unintentionally included in user action names because the confidential data itself is included in an HTML element label, attribute, or other value (for example, click on "my Account Number: 1231231"...). If such confidential data appears in your application's user action names, enable the Mask user action names setting. This setting replaces specific HTML element names and values with generic HTML element names. With user-action name masking enabled, the user action names listed above appear as:

    • click on INPUT on page /search.html
    • keypress on TEXTAREA on page /contact.html
    • touch on DIV of page /list.jsf
    ipAddressMasking string
    Possible Values: All, Public

    Deprecated: This property is not supported anymore by the Dynatrace REST API (since schema version 4)

    ipAddressMaskingEnabled boolean

    Dynatrace captures the IP addresses of your end-users to determine the regions from which they access your application. To learn more, visit Mask IPs and GPS coordinates.. Dynatrace also captures GPS data from mobile apps that provide their users with the option of sharing geolocation data. On the server side, Dynatrace captures IP addresses to enable detailed troubleshooting for Dynatrace service calls.

    Once enabled, IP address masking sets the last octet of monitored IPv4 addresses and the last 80 bits of IPv6 addresses to zeroes. GPS coordinates are rounded up to 1 decimal place (~10 km). This masking occurs in memory. Full IP addresses are never written to disk. Location lookups are made using anonymized IP addresses and GPS coordinates.

    Deprecated: This property is not supported anymore by the Dynatrace REST API (since schema version 4)

    personal_data_uri_masking_enabled bool
    Dynatrace captures the URIs and request headers sent from desktop and mobile browsers. Dynatrace also captures full URIs on the server-side to enable detailed performance analysis of your applications. For complete details, visit Mask personal data in URIs.. URIs and request headers contain personal data. When this setting is enabled, Dynatrace automatically detects UUIDs, credit card numbers, email addresses, IP addresses, and other IDs and replaces those values with placeholders. The personal data is then masked in PurePath analysis, error analysis, user action naming for RUM, and elsewhere in Dynatrace.
    user_action_masking_enabled bool

    When Dynatrace detects a user action that triggers a page load or an AJAX/XHR action. To learn more about masking user actions, visit Mask user actions.. When Dynatrace detects a user action that triggers a page load or an AJAX/XHR action, it constructs a name for the user action based on:

    • User event type (click on..., loading of page..., or keypress on...)
    • Title, caption, label, value, ID, className, or other available property of the related HTML element (for example, an image, button, checkbox, or text input field).

    In most instances, the default approach to user-action naming works well, resulting in user-action names such as:

    • click on "Search" on page /search.html
    • keypress on "Feedback" on page /contact.html
    • touch on "Homescreen" of page /list.jsf

    In rare circumstances, confidential data (for example, email addresses, usernames, or account numbers) can be unintentionally included in user action names because the confidential data itself is included in an HTML element label, attribute, or other value (for example, click on "my Account Number: 1231231"...). If such confidential data appears in your application's user action names, enable the Mask user action names setting. This setting replaces specific HTML element names and values with generic HTML element names. With user-action name masking enabled, the user action names listed above appear as:

    • click on INPUT on page /search.html
    • keypress on TEXTAREA on page /contact.html
    • touch on DIV of page /list.jsf
    ip_address_masking str
    Possible Values: All, Public

    Deprecated: This property is not supported anymore by the Dynatrace REST API (since schema version 4)

    ip_address_masking_enabled bool

    Dynatrace captures the IP addresses of your end-users to determine the regions from which they access your application. To learn more, visit Mask IPs and GPS coordinates.. Dynatrace also captures GPS data from mobile apps that provide their users with the option of sharing geolocation data. On the server side, Dynatrace captures IP addresses to enable detailed troubleshooting for Dynatrace service calls.

    Once enabled, IP address masking sets the last octet of monitored IPv4 addresses and the last 80 bits of IPv6 addresses to zeroes. GPS coordinates are rounded up to 1 decimal place (~10 km). This masking occurs in memory. Full IP addresses are never written to disk. Location lookups are made using anonymized IP addresses and GPS coordinates.

    Deprecated: This property is not supported anymore by the Dynatrace REST API (since schema version 4)

    personalDataUriMaskingEnabled Boolean
    Dynatrace captures the URIs and request headers sent from desktop and mobile browsers. Dynatrace also captures full URIs on the server-side to enable detailed performance analysis of your applications. For complete details, visit Mask personal data in URIs.. URIs and request headers contain personal data. When this setting is enabled, Dynatrace automatically detects UUIDs, credit card numbers, email addresses, IP addresses, and other IDs and replaces those values with placeholders. The personal data is then masked in PurePath analysis, error analysis, user action naming for RUM, and elsewhere in Dynatrace.
    userActionMaskingEnabled Boolean

    When Dynatrace detects a user action that triggers a page load or an AJAX/XHR action. To learn more about masking user actions, visit Mask user actions.. When Dynatrace detects a user action that triggers a page load or an AJAX/XHR action, it constructs a name for the user action based on:

    • User event type (click on..., loading of page..., or keypress on...)
    • Title, caption, label, value, ID, className, or other available property of the related HTML element (for example, an image, button, checkbox, or text input field).

    In most instances, the default approach to user-action naming works well, resulting in user-action names such as:

    • click on "Search" on page /search.html
    • keypress on "Feedback" on page /contact.html
    • touch on "Homescreen" of page /list.jsf

    In rare circumstances, confidential data (for example, email addresses, usernames, or account numbers) can be unintentionally included in user action names because the confidential data itself is included in an HTML element label, attribute, or other value (for example, click on "my Account Number: 1231231"...). If such confidential data appears in your application's user action names, enable the Mask user action names setting. This setting replaces specific HTML element names and values with generic HTML element names. With user-action name masking enabled, the user action names listed above appear as:

    • click on INPUT on page /search.html
    • keypress on TEXTAREA on page /contact.html
    • touch on DIV of page /list.jsf
    ipAddressMasking String
    Possible Values: All, Public

    Deprecated: This property is not supported anymore by the Dynatrace REST API (since schema version 4)

    ipAddressMaskingEnabled Boolean

    Dynatrace captures the IP addresses of your end-users to determine the regions from which they access your application. To learn more, visit Mask IPs and GPS coordinates.. Dynatrace also captures GPS data from mobile apps that provide their users with the option of sharing geolocation data. On the server side, Dynatrace captures IP addresses to enable detailed troubleshooting for Dynatrace service calls.

    Once enabled, IP address masking sets the last octet of monitored IPv4 addresses and the last 80 bits of IPv6 addresses to zeroes. GPS coordinates are rounded up to 1 decimal place (~10 km). This masking occurs in memory. Full IP addresses are never written to disk. Location lookups are made using anonymized IP addresses and GPS coordinates.

    Deprecated: This property is not supported anymore by the Dynatrace REST API (since schema version 4)

    DataPrivacyUserTracking, DataPrivacyUserTrackingArgs

    PersistentCookieEnabled bool
    When enabled, Dynatrace places a persistent cookie on all end-user devices to identify returning users.
    PersistentCookieEnabled bool
    When enabled, Dynatrace places a persistent cookie on all end-user devices to identify returning users.
    persistentCookieEnabled Boolean
    When enabled, Dynatrace places a persistent cookie on all end-user devices to identify returning users.
    persistentCookieEnabled boolean
    When enabled, Dynatrace places a persistent cookie on all end-user devices to identify returning users.
    persistent_cookie_enabled bool
    When enabled, Dynatrace places a persistent cookie on all end-user devices to identify returning users.
    persistentCookieEnabled Boolean
    When enabled, Dynatrace places a persistent cookie on all end-user devices to identify returning users.

    Package Details

    Repository
    dynatrace pulumiverse/pulumi-dynatrace
    License
    Apache-2.0
    Notes
    This Pulumi package is based on the dynatrace Terraform Provider.
    dynatrace logo
    Dynatrace v0.16.0 published on Tuesday, Sep 10, 2024 by Pulumiverse
    pulumiverse/pulumi-dynatrace