Skip to content
This repository has been archived by the owner on Oct 21, 2024. It is now read-only.

Pipe character bug fix with tests #2

Merged
merged 13 commits into from
Apr 27, 2018
Merged

Pipe character bug fix with tests #2

merged 13 commits into from
Apr 27, 2018

Conversation

rue-mchang
Copy link

Metrics sent through connect-datadog cannot contain a route with a pipe character, since the pipe character is used as a delimiter. This fix replaces the pipe character with a configurable replacement character.

We also introduce a few additional improvements, including:

  • Ability to append the baseUrl to the path in the tags
  • A new unit test suite with Jest.

rue-mchang and others added 13 commits February 26, 2018 13:33
Bug fix: Sending metrics with pipes in the route
- Configurable with 'method' option on middleware initialization
It already existed so adding the code was not the appropriate path to take. In the mean time, I standardized the `method` option to be treated similarly to how the other options are treated
That’s now part of test setup for the request object
New unit tests for connect-datadog library
Copy link

@ofek ofek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your contribution!

@ofek ofek merged commit cc04b2d into DataDog:master Apr 27, 2018
@saveman71
Copy link

Hello there, I was looking at #14 and could not find (quickly enough) a source on the "delimiter" that pipe would be on DataDog. Do you have a documentation link maybe?

@saveman71
Copy link

Found it: https://docs.datadoghq.com/tagging/#defining-tags

It however says invalid characters are converted to underscores by default. I'm wondering what's the best course of action to take for more complicated regexes: for example, I have: /^\/(invitation|invite)\/(.*)$/i.

As I understand, it would be converted to /_____invitation-invite_________/_ which doesn't sound ideal.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants