You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[exporter/syslog] Fix handling of multiple structured data elements (#37927)
#### Description
As reported in issue #33300 this fixes the issue when there are more
than one structured data block in the structured_data attributes object.
Say you had a structured block like this:
```json
{
"structured_data": {
"a@123": {
"a": "123"
},
"b@321": {
"b": "321"
}
}
}
```
The expected output would then be two sd blocks, like [a@193
a="123"][b@193 b="321"]
, but instead the code returns one array, like [a@193 a="123" b@193
b="321"] which is wrong according to the
[RFC5424](https://datatracker.ietf.org/doc/html/rfc5424#section-6.3.5)
#### Link to tracking issue
Fixes#33300
#### Testing
A new test for "more than one SD field" was added in the commit, which
failed for the original code, but passes now with the fix.
#### Documentation
No documentation change needed.
---------
Co-authored-by: Andrzej Stencel <[email protected]>
# Use this changelog template to create an entry for release notes.
2
+
3
+
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
4
+
change_type: bug_fix
5
+
6
+
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
7
+
component: syslogexporter
8
+
9
+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10
+
note: Fixes handling of multiple structured data elements
11
+
12
+
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
13
+
issues: [33300]
14
+
15
+
# (Optional) One or more lines of additional information to render under the primary note.
16
+
# These lines will be padded with 2 spaces and then inserted directly into the document.
17
+
# Use pipe (|) for multiline entries.
18
+
subtext: Previous version added all structured data within one bracket pair. According to the RFC each structured data element should have its own bracket pair.
19
+
20
+
# If your change doesn't affect end users or the exported elements of any package,
21
+
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
22
+
# Optional: The change log or logs in which this entry should be included.
23
+
# e.g. '[user]' or '[user, api]'
24
+
# Include 'user' if the change is relevant to end users.
25
+
# Include 'api' if there is a change to a library API.
0 commit comments