Create or delete security context for monitored entities.
Matching entities will have a management zone assigned if the given security context matches the name of an already existing management zone. This endpoint does not create a new management zone if there is no management zone with the provided name.
Management zone rules will not apply to entities with a set security context. To be able to apply them again, you need to delete the security context.
For more information on security context, see Grant access to entities with security context.
The request consumes and produces an application/json payload.
| POST | SaaS | https://{your-environment-id}.live.dynatrace.com/api/v2/entities/securityContext |
| Environment ActiveGateCluster ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/v2/entities/securityContext |
To execute this request, you need an access token with settings.write scope.
To learn how to obtain and use it, see Tokens and authentication.
Defines the scope of the entities to set the security context for. Only entities that can have management zones are considered for this operation
You must set one of these criteria:
type("TYPE")entityId("id"). You can specify several IDs, separated by a comma (entityId("id-1","id-2")). All requested entities must be of the same type.You can add one or more of the following criteria. Values are case-sensitive and the EQUALS operator is used unless otherwise specified.
tag("value"). Tags in [context]key:value, key:value, and value formats are detected and parsed automatically. Any colons (:) that are part of the key or value must be escaped with a backslash(\). Otherwise, it will be interpreted as the separator between the key and the value. All tag values are case-sensitive.mzId(123)mzName("value")entityName.equals: performs a non-casesensitive EQUALS query.entityName.startsWith: changes the operator to BEGINS WITH.entityName.in: enables you to provide multiple values. The EQUALS operator applies.caseSensitive(entityName.equals("value")): takes any entity name criterion as an argument and makes the value case-sensitive.healthState("HEALTHY")firstSeenTms.<operator>(now-3h). Use any timestamp format from the from/to parameters.
The following operators are available:
lte: earlier than or at the specified timelt: earlier than the specified timegte: later than or at the specified timegt: later than the specified time<attribute>("value1","value2") and <attribute>.exists(). To fetch the list of available attributes, execute the GET entity type request and check the properties field of the response.fromRelationships.<relationshipName>() and toRelationships.<relationshipName>(). This criterion takes an entity selector as an attribute. To fetch the list of available relationships, execute the GET entity type request and check the fromRelationships and toRelationships fields.not(<criterion>). Inverts any criterion except for type.For more information, see Entity selector in Dynatrace Documentation.
To set several criteria, separate them with a comma (,). For example, type("HOST"),healthState("HEALTHY"). Only results matching all criteria are included in the response.
The maximum string length is 2,000 characters.
The start of the requested timeframe.
You can use one of the following formats:
2021-01-25T05:57:01.123+01:00. If no time zone is specified, UTC is used. You can use a space character instead of the T. Seconds and fractions of a second are optional.now-NU/A, where N is the amount of time, U is the unit of time, and A is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, now-1y/w is one year back, aligned by a week.
You can also specify relative timeframe without an alignment: now-NU.
Supported time units for the relative timeframe are:
m: minutesh: hoursd: daysw: weeksM: monthsy: yearsIf not set, the relative timeframe of three days is used (now-3d).
The end of the requested timeframe.
You can use one of the following formats:
2021-01-25T05:57:01.123+01:00. If no time zone is specified, UTC is used. You can use a space character instead of the T. Seconds and fractions of a second are optional.now-NU/A, where N is the amount of time, U is the unit of time, and A is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, now-1y/w is one year back, aligned by a week.
You can also specify relative timeframe without an alignment: now-NU.
Supported time units for the relative timeframe are:
m: minutesh: hoursd: daysw: weeksM: monthsy: yearsIf not set, the current timestamp is used.
The JSON body of the request. Contains security context to be set for the matching entities.
SecurityContextDtoImpl objectThe security context, that will be set for matching entities. If there exists a management zone with this name, it will be set for all matching entities, overriding all automatic management zone rules.
This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request.
{"securityContext": ["string"]}
SecurityContextResultDto objectThe response payload holding the result of the security context application.
The entity ids that matched the entity selector and now have the supplied security context set.
The management zone ids that is applied to the entity ids, if the security context matched an existing management zone's name, otherwise null.
{"entityIds": ["string"],"managementZoneIds": [1]}
| DELETE | SaaS | https://{your-environment-id}.live.dynatrace.com/api/v2/entities/securityContext |
| Environment ActiveGateCluster ActiveGate | https://{your-activegate-domain}:9999/e/{your-environment-id}/api/v2/entities/securityContext |
To execute this request, you need an access token with settings.write scope.
To learn how to obtain and use it, see Tokens and authentication.
Defines the scope of the entities to set the security context for. Only entities that can have management zones are considered for this operation
You must set one of these criteria:
type("TYPE")entityId("id"). You can specify several IDs, separated by a comma (entityId("id-1","id-2")). All requested entities must be of the same type.You can add one or more of the following criteria. Values are case-sensitive and the EQUALS operator is used unless otherwise specified.
tag("value"). Tags in [context]key:value, key:value, and value formats are detected and parsed automatically. Any colons (:) that are part of the key or value must be escaped with a backslash(\). Otherwise, it will be interpreted as the separator between the key and the value. All tag values are case-sensitive.mzId(123)mzName("value")entityName.equals: performs a non-casesensitive EQUALS query.entityName.startsWith: changes the operator to BEGINS WITH.entityName.in: enables you to provide multiple values. The EQUALS operator applies.caseSensitive(entityName.equals("value")): takes any entity name criterion as an argument and makes the value case-sensitive.healthState("HEALTHY")firstSeenTms.<operator>(now-3h). Use any timestamp format from the from/to parameters.
The following operators are available:
lte: earlier than or at the specified timelt: earlier than the specified timegte: later than or at the specified timegt: later than the specified time<attribute>("value1","value2") and <attribute>.exists(). To fetch the list of available attributes, execute the GET entity type request and check the properties field of the response.fromRelationships.<relationshipName>() and toRelationships.<relationshipName>(). This criterion takes an entity selector as an attribute. To fetch the list of available relationships, execute the GET entity type request and check the fromRelationships and toRelationships fields.not(<criterion>). Inverts any criterion except for type.For more information, see Entity selector in Dynatrace Documentation.
To set several criteria, separate them with a comma (,). For example, type("HOST"),healthState("HEALTHY"). Only results matching all criteria are included in the response.
The maximum string length is 2,000 characters.
The start of the requested timeframe.
You can use one of the following formats:
2021-01-25T05:57:01.123+01:00. If no time zone is specified, UTC is used. You can use a space character instead of the T. Seconds and fractions of a second are optional.now-NU/A, where N is the amount of time, U is the unit of time, and A is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, now-1y/w is one year back, aligned by a week.
You can also specify relative timeframe without an alignment: now-NU.
Supported time units for the relative timeframe are:
m: minutesh: hoursd: daysw: weeksM: monthsy: yearsIf not set, the relative timeframe of three days is used (now-3d).
The end of the requested timeframe.
You can use one of the following formats:
2021-01-25T05:57:01.123+01:00. If no time zone is specified, UTC is used. You can use a space character instead of the T. Seconds and fractions of a second are optional.now-NU/A, where N is the amount of time, U is the unit of time, and A is an alignment. The alignment rounds all the smaller values to the nearest zero in the past. For example, now-1y/w is one year back, aligned by a week.
You can also specify relative timeframe without an alignment: now-NU.
Supported time units for the relative timeframe are:
m: minutesh: hoursd: daysw: weeksM: monthsy: yearsIf not set, the current timestamp is used.
SecurityContextResultDto objectThe response payload holding the result of the security context application.
The entity ids that matched the entity selector and now have the supplied security context set.
The management zone ids that is applied to the entity ids, if the security context matched an existing management zone's name, otherwise null.
{"entityIds": ["string"],"managementZoneIds": [1]}