-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(new_relic sink): Put log API attributes in separate structure (#2…
…1313) * fix(new_relic sink): Put log API attributes in separate structure The New Relic log API specifies that all attributes other than `message` and `timestamp` should go into an `attributes` field, which may contain any JSON object data except for arrays. This change reworks the logs API model to move all attributes from the log event into this attributes field as well as using structures to encode fields with fixed names instead of using dynamic maps. The tests have also been updated to compare the overall structure of the output data model so as to ensure that the resulting encoding generated by `serde` matches what we is specified in the New Relic API documentation. * Add change log entry
- Loading branch information
Showing
4 changed files
with
196 additions
and
106 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
Previously, when the `new_relic` sink sent non-standard event fields to the logs | ||
API, it would include those fields beside the standard event fields (i.e. | ||
`message` and `timestamp`). Now, any such fields are sent in an `attributes` | ||
object, as specified by the New Relic logs API documentation. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.