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
Describe the bug
The Scalyr logger has 2 configuration settings (sessioninfo and attrs) that can contain arbitrary key-value pairs. This is extra information sent alongside the data. This is configured as follows:
I had a look at the code and am not convinced this will be an easy fix, seem as how the keys are actually checked. It looks like the whole config checker might need a re-design :(
I agree with you, the complexity of the config checker is too high, a complete redesign is needed. Any helps are welcome :)
In the meantime, I will push a quick and dirty fix :(
Describe the bug
The Scalyr logger has 2 configuration settings (
sessioninfo
andattrs
) that can contain arbitrary key-value pairs. This is extra information sent alongside the data. This is configured as follows:When starting go-dnscollector, it errors (key name might differ, based on parsing order):
To Reproduce
Configure the scalyr logger as shown above, start go-dnscollector.
Expected behavior
go-dnscollector starts fine.
Additional context
These fields in the config are a
map[string]string
and amap[string]interface{}
.https://github.com/dmachard/go-dnscollector/blob/0267e3b47aa374b51df84ceacb61238258d3fdea/pkgconfig/loggers.go#L239-L240
Perhaps these field types should be ignored when converting the config to a map before checking it?
The text was updated successfully, but these errors were encountered: