Service detection rule for Web service

[alapatiharsha]

I am creating the service detection rule based on the URL Path for that web service,

It was like /users/............/Identity/verify

the above mentioned ".........." are represented as Customer ID for the web service, whenever that service was getting traffic, it creates a new service using the cust id (lots of services are creating) 

I am giving the condition as Url Path ends with /identity/verify 

any suggestions here please.

[Julius_Loman]

Most likely you need to override the detected URL context root to a fixed value like this:

[Julius_Loman]

Based on the description of your situation, this should do the trick. If not, please provide a screenshot of  service properties for a service in your case.

[Julius_Loman]

You are confusing services and requests.
What you have shown is a request. You already have the requests in one service. Please provide service properties for services you would like to merge:

[Peter_Youssef]

Hello @alapatiharsha 

• The attached images related to the requests which are parts of the URL but these aren't the URLs.
• You can configure "Remove numbers" within the current service detection rule.
• You can either override to constant value or use the transformed value.
• If you proceeded with use constant value the related request will be grouped under the new service.

Hoping it helps.

BR,

Peter

[alapatiharsha]

Could you please guide me with some screen shots. 

[Peter_Youssef]

Hi @alapatiharsha 
As an example of removing the numbers PFA screenshot

Regards,

Peter

[Peter_Youssef]

Hi @alapatiharsha 

an example for service detection:

Best of luck.

Regards,

Peter

[Peter_Youssef]

Hello @alapatiharsha 

You can refer to the solution provided by @Julius_Loman and Dynatrace Docs for further guidance:

• https://docs.dynatrace.com/docs/observe/applications-and-microservices/services/service-detection-an...
• https://docs.dynatrace.com/docs/observe/applications-and-microservices/services/service-detection-an...
• Advanced cases https://docs.dynatrace.com/docs/discover-dynatrace/references/dynatrace-api/environment-api/settings...

Dynatrace offers the below contribution types' options for service detection rules, you can specify as per the actual service segments and how the service should be presented as service detection rules impact both the detection and naming as well:

• Use the transformed value:

Means the new service name after applying any of the available transformation methods:

• "Application identifier: transform this value before letting it contribute to the service Id

OR

• "Server Name: transform this value before letting it contribute to the service Id " 

OR

• "URL context root: transform this value before letting it contribute to the service Id" you can use single or combined options  based on the actual scenario as per the shown service properties through the UI.

• Use the Original value:

it will keep the original detected service name.

• Override to constant value:

Whatever will be detected will be overwritten to the provided value, all requests will be grouped beneath it accordingly.

Hoping it adds value.

BR, 

Peter