# Transaction.name have url repeated twice

**URL:** <https://discuss.elastic.co/t/transaction-name-have-url-repeated-twice/182157>\
**Category:** APM\
**Tags:** nodejs\
**Created:** [May 22, 2019, 7:30am UTC](https://discuss.elastic.co/t/transaction-name-have-url-repeated-twice/182157 "2019-05-22T07:30:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shashank\_Sah](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shashank_sah/32/46154_2.png) [@Shashank\_Sah](https://discuss.elastic.co/u/Shashank_Sah)\
**Post date:** [May 22, 2019, 7:30am UTC](https://discuss.elastic.co/t/transaction-name-have-url-repeated-twice/182157/1 "2019-05-22T07:30:56Z")

</div>

**Kibana version** : 6.5.1

**Elasticsearch version** : 6.5.1

**APM Server version** : 6.5.1

**APM Agent language and version** : Node 2.9.0

The transaction.name field in apm-\* index is not coming correctly for all of our transactions.  
Value present in index:  
transaction.name:POST /provider-training-service/getFilteredPopulatedUserCampaignData/provider-training-service/getFilteredPopulatedUserCampaignData

Correct Value:  
transaction.name:POST /provider-training-service/getFilteredPopulatedUserCampaignData

Here the value in index contains the same url two times but it should be only once. Please tell how this can be resolved.

---

<div class="post-metadata">

**Author:** ![wa7son](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wa7son/32/21259_2.png) [@wa7son](https://discuss.elastic.co/u/wa7son)\
**Post date:** [May 22, 2019, 7:47am UTC](https://discuss.elastic.co/t/transaction-name-have-url-repeated-twice/182157/2 "2019-05-22T07:47:47Z")

</div>

This sounds related to how we interpret the routes in your framework. Could you share a little more information about your setup:

1. Which framework are you using (module + version)?
2. How are these particular routes configured that this transaction represents?

---

<div class="post-metadata">

**Author:** ![Shashank\_Sah](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shashank_sah/32/46154_2.png) [@Shashank\_Sah](https://discuss.elastic.co/u/Shashank_Sah)\
**Post date:** [May 23, 2019, 9:18am UTC](https://discuss.elastic.co/t/transaction-name-have-url-repeated-twice/182157/3 "2019-05-23T09:18:46Z")

</div>

Hi Thomas,  
We use express framework with node. Given below are the versions:  
node version: 8.1.0  
express version: 4.17.0  
cls-hooked: 4.2.2 as middleware for creating session context

Given below is how we are making service calls:

```javascript
var options = {
        method: 'POST',
        uri: 'http://' + server_host + ':' + server_port + '/' + called_service_id + '/' + method_name,
        qs: {
          trxn_id: trxn_id,
          client_id: service_id
        },
        body: req,
        json: true,
        timeout: TIMEOUT_MSEC
      };

```

Please tell if I need to provide any more information.

Thanks,  
Shashank

---

<div class="post-metadata">

**Author:** ![wa7son](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wa7son/32/21259_2.png) [@wa7son](https://discuss.elastic.co/u/wa7son)\
**Post date:** [May 23, 2019, 9:38am UTC](https://discuss.elastic.co/t/transaction-name-have-url-repeated-twice/182157/4 "2019-05-23T09:38:36Z")

</div>

Thanks for the details.

This is most likely related to how the routes in Express are configured (e.g. if you're mounting sub-routes etc). It's not something we've seen before, but there's many ways of configuring routes in Express - and our test suite might not cover all of them. It would therefore be a great help if you could share an example app that reproduces the problem.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 13, 2019, 5:49am UTC](https://discuss.elastic.co/t/transaction-name-have-url-repeated-twice/182157/5 "2019-06-13T05:49:44Z")

</div>

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.