Source field becomes incorrect when ingesting netflow data to graylog docker container
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 30/100
- Issue 类型
- 缺陷
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- docker, java
- 领域
- networking
调研方向
从 Netflow 输入入口开始，使用文档中的 Docker 设置、Graylog 4.0.1 和重启容器来复现 source 字段的变更。跟踪重启前后 Netflow source 的记录方式；当记录继续显示源 probe 的 IP，而不是 Docker 网络网关的 IP 时，即表示完成。
由索引模型根据 Issue 内容生成。
描述
Expected Behavior
Source field should be correct and show the IP of the Netflow source
Current Behavior
TLDR: In graylog container, something triggers the netflow input to switch from storing the correct source field to storing the internal gateway IP for the docker network the container is in.
I'm running graylog, elasticsearch and mongo as containers from a docker-compose file more or less the same as that given in the documentation.
I have a Netflow input set up, override_source is not set. Into that I am feeding Netflow v9 records from two different systems, running different netflow probe software (a Linux box running netprobe and a BSD box running softflowd). All is well, and the data is correct. At some point, something happens, and the source field in the data changes from the IP of the netflow probe machine to the IP of the internal gateway of the docker network. This happens to data from both netflow probe machines.
I believe from a small amount of testing that the 'something' that triggers it is the restart of the docker container, whether by the host updating docker or stopping/starting the container. That certainly seemed to cause it to start to use the docker host's IP as the source rather than the actual IPs but there may be other triggers.
Once in that state, restarting the probe software on the remote boxes seems to be the only way to get it to start logging the correct source field again.
The issue does seem to be specific to the Netflow module, other inputs (beats, syslog) are working fine. I can't currently test whether there's any way to trigger the same issue on a non-container version.
Context
It's problematic if I want to search based on which box sent netflow data, or to apply pipeline rules to normalize the data coming from the two sources if I relied on that obvious field to tell the sources apart.
Your Environment
- Graylog Version: Graylog 4.0.1+6a0cc0b (docker container tag graylog/graylog:4.0)
- Java Version: 1.8.0_275
- Elasticsearch Version: 7.10.1 (docker container tag elasticsearch-oss:7.10.1)
- MongoDB Version: 3 (docker container tag mongo:3)
- Operating System: Ubuntu 18.04
- Browser version:
- Docker version: 20.10.2
- 主要语言
- Java
- 星标
- 17
- 派生
- 13
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Graylog2/graylog-plugin-integrations 的其他 Issue
-
bug triaged
难度 4/5 3-5 天 新手友好度 25/100
Graylog2/graylog-plugin-integrations#1350 · 3 条评论 ·
-
Wrong link in README.md可能已有人在做 @JSap0914 于 126 天前认领。 未关闭bug triaged
难度 1/5 1 小时以内 新手友好度 45/100
Graylog2/graylog-plugin-integrations#1339 · 2 个 reaction ·
-
bug triaged
难度 4/5 3-5 天 新手友好度 25/100
Graylog2/graylog-plugin-integrations#1338 · 3 条评论 ·
-
Pager Duty Additional fields可能重新可做 @deepakmadisetty 于 1493 天前认领，目前没有进行中的 PR。 未关闭feature triaged
难度 2/5 1-3 小时 新手友好度 45/100
Graylog2/graylog-plugin-integrations#1157 · 2 条评论 ·
-
Update GreyNoise Community IP Lookup Adapter可能重新可做 @roberto-graylog 于 1769 天前认领，目前没有进行中的 PR。 未关闭feature
Graylog2/graylog-plugin-integrations#957 · 已指派 1 人 ·
查看 Graylog2/graylog-plugin-integrations 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
pdfium-drift
难度 1/5 1 小时以内 新手友好度 84/100
Stirling-Tools/JPDFium#240 ·
维护者通常 1 天内回复
-
Bug
难度 2/5 1-3 小时 新手友好度 60/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 86/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 68/100
Vakore/ZappierGames#285 ·