influxdata / influxdata/kapacitor
kapacitor自定义检测日志生成问题
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
你好,根据这个文档kapacitor已经成功启动,但是却没生成对应的的日志文件,对比成功案例,会生成三个不同的日志文件,如下: (Translation: (Hello, according to this document, Kapacitor has been successfully started, but the corresponding log file has not been generated. Comparing successful cases, three different log files will be generated, as follows:)
air_failure.log
bed_failure.log
hotend_failure.log
;
个人对比成功案例,怀疑是因为kapacitor缺少了python调用ttest.py脚本文件的进程导致无法生成日志文件 (Translation: Personal comparison of successful cases, it is suspected that Kapacitor lacks the process of python to call the ttest.py script file, which makes it impossible to generate log files)
ps -ef | grep kapacitor
root 21831 1 16 16:37 ? 00:00:00 /usr/bin/kapacitord -config /etc/kapacitor/kapacitor.conf
root 21865 21831 99 16:37 ? 00:00:01 /usr/bin/python2 -u /tmp/kapacitor_udf/ttest.py
root 21866 21831 99 16:37 ? 00:00:01 /usr/bin/python2 -u /tmp/kapacitor_udf/ttest.py
root 21867 21831 93 16:37 ? 00:00:00 /usr/bin/python2 -u /tmp/kapacitor_udf/ttest.py
Ps:这里使用root启动的kapacitor的服务
还请求助,谢谢 (Translation: Ps: Here is the service of Kapacitor started by root
Also ask for help, thank you)
Contributor guide
Research direction
Start by reviewing the Kapacitor startup configuration in /etc/kapacitor/kapacitor.conf and the referenced ttest.py UDF process. Reproduce the service startup and inspect whether the three expected log files are created while checking the kapacitord and Python process output. Done means the missing log-generation cause is identified and the expected logging behavior is restored or clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, python
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100