• Home
  • Dynatrace API
  • Configuration
  • Services
  • Custom services
  • PUT reorder rules

Custom services API - PUT reorder rules

Custom service rules are evaluated from top to bottom; the first matching rule applies.

This request reorders the custom service rules according to the order of the IDs in the body of the request. Rules that are omitted from the body of the request will retain their relative order but will be placed after all those present in the request.

The request consumes an application/json payload.

PUTManagedDynatrace for Governmenthttps://{your-domain}/e/{your-environment-id}/api/config/v1/service/customServices/{technology}/order
SaaShttps://{your-environment-id}.live.dynatrace.com/api/config/v1/service/customServices/{technology}/order
Environment ActiveGatehttps://{your-activegate-domain}/e/{your-environment-id}/api/config/v1/service/customServices/{technology}/order

Authentication

To execute this request, you need an access token with WriteConfig scope.

To learn how to obtain and use it, see Tokens and authentication.

Parameters

ParameterTypeDescriptionInRequired
technologystring

Technology of custom services to update.

The element can hold these values
  • dotNet
  • go
  • java
  • nodeJS
  • php
pathrequired
bodyStubList

JSON body of the request containing the IDs of the custom services in the desired order. Any further properties (name, description) will be ignored.

bodyoptional

Request body objects

The StubList object

An ordered list of short representations of Dynatrace entities.

ElementTypeDescriptionRequired
valuesEntityShortRepresentation[]

An ordered list of short representations of Dynatrace entities.

required

The EntityShortRepresentation object

The short representation of a Dynatrace entity.

ElementTypeDescriptionRequired
idstring

The ID of the Dynatrace entity.

required
namestring

The name of the Dynatrace entity.

optional
descriptionstring

A short description of the Dynatrace entity.

optional

Request body JSON model

This is a model of the request body, showing the possible elements. It has to be adjusted for usage in an actual request.

json
{ "values": [ { "id": "6a98d7bc-abb9-44f8-ae6a-73e68e71812a", "name": "Dynatrace entity 1", "description": "Dynatrace entity 1 for the REST API example" }, { "id": "ee70f7d3-9a4e-4f5f-94d2-c9d6156f1618", "name": "Dynatrace entity 2" }, { "id": "8cdabe77-9e1a-4be8-b3df-269dd6fa9d7f" } ] }

Response

Response codes

CodeTypeDescription
204

Success. Custom services have been updated. Response doesn't have a body.

400ErrorEnvelope

Failed. The input is invalid

Related topics
  • Define custom services

    Define entry points (a method, class, or interface) for custom services that don't use standard protocols.