-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: remove built in payload truncation logic #498
Conversation
@@ -37,7 +37,7 @@ test('extract URL from request', function (t) { | |||
t.equal(request.url.search, '?foo=bar') | |||
t.equal(request.url.raw, '/captureError?foo=bar') | |||
t.equal(request.url.hostname, 'localhost') | |||
t.equal(request.url.port, String(server.info.port)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤔 Previously, the act of truncating this property would convert it to a string. Now that truncation isn't part of this module any more, it's a number. But that's technically not a legal type for this property according to the intake API JSON spec:
Should the JSON spec allow for a number here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we even truncate ports? They can't ever be longer than 5 digits. 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When implementing the truncation logic, I just went over all strings that had a limit on them and added the truncation.
Using a filter the user can overwrite it with anything they want. You could argue though that if they did the server JSON schema validation would just reject it, so it might not be that important.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In related news, I realized the other day that process.title
cannot be more than 16 bytes on Linux
The CI failures are because of the npm bug with the github link in the dependencies |
This will instead be handled by the elastic-apm-http-client module in the future.
This will instead be handled by the elastic-apm-http-client module in the future.
This will instead be handled by the elastic-apm-http-client module in the future.
This will instead be handled by the elastic-apm-http-client module in the future.
This will instead be handled by the elastic-apm-http-client module in the future.
This will instead be handled by the elastic-apm-http-client module in the future.
This will instead be handled by the elastic-apm-http-client module in the future.
This will instead be handled by the elastic-apm-http-client module in the future.
This will instead be handled by the elastic-apm-http-client module in the future.
This will instead be handled by the elastic-apm-http-client module in the future.
This will instead be handled by the elastic-apm-http-client module in the future.
This will instead be handled by the elastic-apm-http-client module in the future.
This will instead be handled by the elastic-apm-http-client module in the future.
This will instead be handled by the elastic-apm-http-client module in the future.
This will instead be handled by the elastic-apm-http-client module in the future.
This will instead be handled by the elastic-apm-http-client module in the future.
This will instead be handled by the elastic-apm-http-client module in the future.
Changes for intake API v2.
Depends on elastic/apm-nodejs-http-client#8
This will instead be handled by the elastic-apm-http-client module when the above PR have been merged.