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
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Use Cases
We are currently migrating away from Logstash, but due to some scripts our clients use the fields need to be 1:1 identical to what Logstash generates. I have the following in my current vector configuration and it's needed in 3 different places.
Also, the if ip_cidr_contains block is repeated in other places as well. It would be very useful if I could define my own is_bogon and massage_geodata functions and use them across my configuration
Attempted Solutions
One workaround I was thinking of was to store the geo data in a variable and then have that geo data manipulated by a VRL stored in a file. This would work for the massage_geodata function, but not for is_bogon
Proposal
No response
References
No response
Version
0.23.0
The text was updated successfully, but these errors were encountered:
A note for the community
Use Cases
We are currently migrating away from Logstash, but due to some scripts our clients use the fields need to be 1:1 identical to what Logstash generates. I have the following in my current vector configuration and it's needed in 3 different places.
Also, the
if ip_cidr_contains
block is repeated in other places as well. It would be very useful if I could define my ownis_bogon
andmassage_geodata
functions and use them across my configurationAttempted Solutions
One workaround I was thinking of was to store the geo data in a variable and then have that geo data manipulated by a VRL stored in a file. This would work for the
massage_geodata
function, but not foris_bogon
Proposal
No response
References
No response
Version
0.23.0
The text was updated successfully, but these errors were encountered: