Incorrect URL shown in Pulse

frederikprijck

Posted on
Jun 03 2016

Dear,

I am running a trial for Pulse in order to inspect whether or not it has the functionality we need. However, i stumbled upon the following problem.

I have the following HTTP Body which is being Posted to api.raygun.io/events?apikey=[key]

{
  "eventData": [
    {
      "sessionId": "xuqtf8q14wwk8g4kswwwswkc0wo8cos4",
      "timestamp": "2016-06-02T12:45:31.045Z",
      "type": "web_request_timing",
      "user": {
        "Identifier": "test_identifier",
        "IsAnonymous": false
      },
      "version": "Not supplied",
      "device": "Mozilla\/5.0 (Windows NT 6.3; WOW64) AppleWebKit\/537.36 (KHTML, like Gecko) Chrome\/51.0.2704.79 Safari\/537.36",
      "data": "[{\"url\":\"http://localhost:9002/demo/-3/2/1/4/0/fr\",\"userAgent\":\"Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36\",\"timing\":{\"t\":\"v\",\"du\":43326.58,\"o\":56914.485},\"size\":0}]"
    }
  ]
}

The Http response:

HTTP/1.1 202 Accepted
Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept
Access-Control-Allow-Origin: *
Content-Type: application/json; charset=utf-8
Date: Thu, 02 Jun 2016 12:45:31 GMT
Server: nginx/1.4.6 (Ubuntu)
Content-Length: 2
Connection: keep-alive

However, raygun shows the following url: enter image description here Edit: Image embedding is not working ? Image can be found at: http://image.prntscr.com/image/16c8e590e6264bee94fb0a3e914aa239.png

As you can see there are some problems:

  • The port has been changed from 9002 to 900*.
  • Some other numbers have been replaced by *.

Is there anything I am missing here?

Thanks

Alex

Posted on
Jun 09 2016

Hi Frederik,

What's happening here is that we are replacing numerical identifiers in your URL with a wildcard. This is a default behavior within our ingestion pipeline to help group similar pages so that you can see aggregate information about base pages instead of every page appearing as a unique entry.

You can read about this behavior here: https://raygun.com/docs/pulse/path-segment-rules

It looks like there is a bug here when wildcarding some of your URLs which caused the end of the port to be replaced as well. We've got a fix coming for this which should be released in the near future.

If you wish to disable or partially disable our default wildcarding behavior we recommend adding some ungrouping rules on your Pulse Settings page

For instance adding: 

http://localhost:9002/demo/*/*/*/*/*/fr

to your ungrouping rules will cause all URL's which match this pattern to not have segments replaced with wild cards.

Feel free to contact us within the Raygun app (click Feedback in the sidebar) if you would like any more help with grouping rules for your URL scheme specifically.

Best regards,
Alex

Reply