Commit 4090455
committed
Set up JSON logging properly for fields
When using the JSON logging backend, tracing expects the fields to have
been formatted as a JSON string. However, the layer wasn't set up
properly for that, resulting in a variety of "field_error"s in the logs
(and panics on debug builds).
As it turns out, we were setting it up in an overcomplicated way
regardless, so use the simpler helper functions in tracing that set all
of this up for us.
Signed-off-by: Ryan Gonzalez <[email protected]>1 parent 542e747 commit 4090455
1 file changed
+17
-31
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
4 | 4 | | |
5 | 5 | | |
6 | 6 | | |
7 | | - | |
8 | | - | |
9 | | - | |
10 | | - | |
11 | | - | |
12 | | - | |
13 | | - | |
14 | | - | |
15 | | - | |
| 7 | + | |
| 8 | + | |
16 | 9 | | |
17 | 10 | | |
18 | 11 | | |
| |||
90 | 83 | | |
91 | 84 | | |
92 | 85 | | |
93 | | - | |
94 | | - | |
95 | | - | |
96 | | - | |
97 | | - | |
98 | | - | |
99 | | - | |
100 | | - | |
101 | | - | |
102 | | - | |
103 | 86 | | |
104 | 87 | | |
105 | 88 | | |
| |||
113 | 96 | | |
114 | 97 | | |
115 | 98 | | |
116 | | - | |
117 | | - | |
118 | | - | |
119 | | - | |
| 99 | + | |
| 100 | + | |
| 101 | + | |
| 102 | + | |
| 103 | + | |
120 | 104 | | |
121 | 105 | | |
122 | | - | |
123 | | - | |
124 | | - | |
125 | | - | |
| 106 | + | |
| 107 | + | |
| 108 | + | |
| 109 | + | |
| 110 | + | |
126 | 111 | | |
127 | 112 | | |
128 | | - | |
129 | | - | |
130 | | - | |
131 | | - | |
| 113 | + | |
| 114 | + | |
| 115 | + | |
| 116 | + | |
| 117 | + | |
132 | 118 | | |
133 | 119 | | |
134 | 120 | | |
| |||
0 commit comments