-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]按照文档一路安装,从1.2-到1.4【logseer】 真用不起 #167
Comments
snpyeso
changed the title
[Bug]按照文档一路安装,从1.2-到1.4, 【audit】【logseer】 这两真用不起
[Bug]按照文档一路安装,从1.2-到1.4【logseer】 这两真用不起
Sep 24, 2022
snpyeso
changed the title
[Bug]按照文档一路安装,从1.2-到1.4【logseer】 这两真用不起
[Bug]按照文档一路安装,从1.2-到1.4【logseer】 真用不起
Sep 24, 2022
应该是logseer读取不到es地址或者es地址无法访问导致的。
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
继续观光一下
【Hotplug】hotplugs.hotplug.kubecube.io v1
common 与 pivot-cluster 都打开
出现一个空指针异常
进入logseer容器
审计可以了,
但是日志依然不通,看来只有想办法开放ES 9200端口出来用工具连连是没上传还是没查询到,
不过大体定位到如下可能的几个问题
费解
目前发现的问题猜测ripple和filebeat的配置感觉这里嫌疑最大,创建了新的日志抓取任务,也没看到/etc/filebeat/inputs.d 有什么文件改动
不过也建议修复下空报错的问题,让指示得更明显,只能去看看哪里有源码了
The text was updated successfully, but these errors were encountered: