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
When configuring the Tyk Pump for Splunk with custom fields specified in the meta.fields section of pump.conf, the expected behavior is for these fields to populate the Splunk events. Cf this part of the code:
ps: I'm receiving the collector token sent in the config, which makes me wonder whether the statement len(p.config.Fields) > 0 is true or not.
Currently, the only method I've found to successfully retrieve the desired fields involves enabling "enable_detailed_recording": true in the tyk.standalone.conf file (utilized for the Tyk Gateway). This approach provides me with the raw_request, which includes a significant amount of the targeted data.
Is my pump.conf configuration might be incorrect ? or is there an alternative method to get these fields without having to depend encoded raw_request?
I appreciate any insights.
Thanks
The text was updated successfully, but these errors were encountered:
When configuring the Tyk Pump for Splunk with custom fields specified in the meta.fields section of pump.conf, the expected behavior is for these fields to populate the Splunk events. Cf this part of the code:
tyk-pump/pumps/splunk.go
Line 209 in 1c28c84
However, despite correct configuration, Tyk Pump disregards these specifications and only sends the default set of fields.
My configuration setup:
I'm running this docker-compose with 3 services :
Here is my Tyk pump.conf file (where I'm configuring the Splunk conf to send to a collector_url of an app running on my host machine on port 7000 :
Issue: even with fields explicitly set in the
meta.fields
field, I'm still receiving on the default list as in this else statementtyk-pump/pumps/splunk.go
Line 226 in 1c28c84
ps: I'm receiving the collector token sent in the config, which makes me wonder whether the statement
len(p.config.Fields) > 0
is true or not.Currently, the only method I've found to successfully retrieve the desired fields involves enabling "enable_detailed_recording": true in the tyk.standalone.conf file (utilized for the Tyk Gateway). This approach provides me with the raw_request, which includes a significant amount of the targeted data.
Is my
pump.conf
configuration might be incorrect ? or is there an alternative method to get these fields without having to depend encodedraw_request
?I appreciate any insights.
Thanks
The text was updated successfully, but these errors were encountered: