Skip to main content
S
sparca1-Visitor
1-Visitor
January 27, 2022
Solved

Error configuring Dynatrace PTC Windchill Starter Set

  • January 27, 2022
  • 4 replies
  • 1968 views

Following instructions from https://github.com/dynatrace-oss/PTC-Windchill, I get an unexpected error; this is the trace of the operation, can someone encountered this error and how to solve?

 

D:\src\Dynatrace-PTC-Windchill>PTC-Windchill_v0.6.6.exe -url https://***.live.dynatrace.com -verbose -token ***
2022/01/27 09:20:20 ==== assets///01-ManagementZones/MgmtZone.json ====
processResponse
2022/01/27 09:20:21 id: 4621721943137380955
2022/01/27 09:20:21 name: PTC
2022/01/27 09:20:21 [ENV] {managementzones.id} <= 4621721943137380955
2022/01/27 09:20:21 ==== assets///02-Application/Application.json ====
processResponse
2022/01/27 09:20:21 id: APPLICATION-90CE01F27D579187
2022/01/27 09:20:21 name: PTC Windchill
2022/01/27 09:20:21 [ENV] {application.id} <= APPLICATION-90CE01F27D579187
2022/01/27 09:20:21 ==== assets///03-DetectionRules/ApplicationDetectionRules.json ====
processResponse
2022/01/27 09:20:21 id: 6d4f6e26-23b0-40e5-b55e-245233eccd03
2022/01/27 09:20:21 name: PTC Windchill
2022/01/27 09:20:21 [ENV] {detectionrules.id} <= 6d4f6e26-23b0-40e5-b55e-245233eccd03
2022/01/27 09:20:21 ==== assets///04-AutoTags/BackgroundMethodServerTag.json ====
processResponse
2022/01/27 09:20:21 id: db8bfa71-5a6a-45e8-be1a-3c73c6901bb5
2022/01/27 09:20:21 name: BackgroundMethodServer
2022/01/27 09:20:21 [ENV] {autotags.id} <= db8bfa71-5a6a-45e8-be1a-3c73c6901bb5
2022/01/27 09:20:21 ==== assets///04-AutoTags/DirectoryServerTag.json ====
processResponse
2022/01/27 09:20:21 id: 13c2f5fb-4d9e-4f87-8b2f-07370049b20d
2022/01/27 09:20:21 name: DirectoryServer
2022/01/27 09:20:21 [ENV] {autotags.id} <= 13c2f5fb-4d9e-4f87-8b2f-07370049b20d
2022/01/27 09:20:21 ==== assets///04-AutoTags/MethodServerTag.json ====
processResponse
2022/01/27 09:20:21 id: d2a1cdc3-2f69-4365-bed1-47789091940a
2022/01/27 09:20:21 name: MethodServer
2022/01/27 09:20:21 [ENV] {autotags.id} <= d2a1cdc3-2f69-4365-bed1-47789091940a
2022/01/27 09:20:21 ==== assets///04-AutoTags/ServerManagerTag.json ====
processResponse
2022/01/27 09:20:21 id: 0ce3ec3e-820e-446a-9b18-4434a6d92df6
2022/01/27 09:20:21 name: ServerManager
2022/01/27 09:20:21 [ENV] {autotags.id} <= 0ce3ec3e-820e-446a-9b18-4434a6d92df6
2022/01/27 09:20:21 ==== assets///05-RequestAttributes/ActionName.json ====
processResponse
2022/01/27 09:20:21 id: ed73dfe2-5dcb-4b4a-900b-46b54603de4d
2022/01/27 09:20:21 name: ActionName
2022/01/27 09:20:21 [ENV] {requestattributes.id} <= ed73dfe2-5dcb-4b4a-900b-46b54603de4d
2022/01/27 09:20:21 ==== assets///05-RequestAttributes/GetRemoteUser.json ====
processResponse
2022/01/27 09:20:21 id: 1a953bf2-f7ff-4c13-96ec-bb749f827cd3
2022/01/27 09:20:21 name: GetRemoteUser
2022/01/27 09:20:21 [ENV] {requestattributes.id} <= 1a953bf2-f7ff-4c13-96ec-bb749f827cd3
2022/01/27 09:20:27 ==== assets///06-MetricsService/ActionNameByUser.json ====
processResponse
panic: {
 "code": 400,
 "message": "Constraints violated.",
 "constraintViolations": [
 {
 "path": "conditions[0].requestAttribute",
 "message": "Condition for unknown request attribute",
 "parameterLocation": "PAYLOAD_BODY",
 "location": ""
 },
 {
 "path": "dimensionDefinition.dimension",
 "message": "Pattern contains unknown request attribute 'GetRemoteUser'.",
 "parameterLocation": "PAYLOAD_BODY",
 "location": ""
 }
 ]
}

goroutine 1 [running]:
main.main()
 github.com/dynatrace-oss/PTCInstaller/main.go:69 +0x160

D:\src\Dynatrace-PTC-Windchill>echo %errorlevel%
2

 

Best answer by sparca

Dynatrace support answered (very quickly):

Quote: "The short explanation is that it happens when the API calls are triggered too quickly between each call. Some API calls are dependent on the execution of previous calls and this error occurs if they are still processing the request in the backend.

To resolve this issue please navigate to the local directory where you downloaded the GitHub files, navigate into the “assets” folder, and delete already loaded files; in my case: folder with the prefix “01” – “05” (“01-ManagementZones”, “02-Application”, “03-DetectionRules”, “04-AutoTags”, “05-RequestAttributes”). After deleting the folders, please re-execute the script.

  • Solution Explanation: The utility tool returns an error and terminates if it sees existing assets already deployed on the tenant. Without deleting the folders above, it’ll attempt to execute the first json (assets/01-ManagementZones/MgmtZone.json) and return an error since it already exists from the previous execution. Deleting the specified folders above will bypass all of the successful API calls from your previous run based off of the log file provided."

This solution worked, but first, in my case, I had to delete the object that give error (ActionNameByUser) you can to this in Settings -> Server-Side Monitoring -> Calculated Service Metrics

4 replies

V
VladimirN24-Ruby IV
24-Ruby IV
January 27, 2022

 Hi,

 

Quote: "Please reach out to PTC@dynatrace.com  for assistance with deploying the starter set or for any questions/concerns".

S
sparca1-VisitorAuthor
1-Visitor
January 27, 2022

Already contacted this address, and asked to share the solution here, if possible.
maybe someone else have similar issues and a public answer can be useful

V
VladimirN24-Ruby IV
24-Ruby IV
January 27, 2022

Ok.

S
sparca1-VisitorAuthorAnswer
1-Visitor
January 27, 2022

Dynatrace support answered (very quickly):

Quote: "The short explanation is that it happens when the API calls are triggered too quickly between each call. Some API calls are dependent on the execution of previous calls and this error occurs if they are still processing the request in the backend.

To resolve this issue please navigate to the local directory where you downloaded the GitHub files, navigate into the “assets” folder, and delete already loaded files; in my case: folder with the prefix “01” – “05” (“01-ManagementZones”, “02-Application”, “03-DetectionRules”, “04-AutoTags”, “05-RequestAttributes”). After deleting the folders, please re-execute the script.

  • Solution Explanation: The utility tool returns an error and terminates if it sees existing assets already deployed on the tenant. Without deleting the folders above, it’ll attempt to execute the first json (assets/01-ManagementZones/MgmtZone.json) and return an error since it already exists from the previous execution. Deleting the specified folders above will bypass all of the successful API calls from your previous run based off of the log file provided."

This solution worked, but first, in my case, I had to delete the object that give error (ActionNameByUser) you can to this in Settings -> Server-Side Monitoring -> Calculated Service Metrics

    Terms & ConditionsAccessibility statement