influxdata / influxdata/kapacitor
Is it a bug?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
i am running kapacitor,but no reponse, i don't know why,please help me !
```
kapacitor record stream -task cpu_alert -duration 20s
```
no relay
The database is new one,
```
kapacitor define cpu_alert -type stream -tick cpu_usage_idle1.tick -dbrp xinmi_login.autogen
kapacitor record stream -task cpu_alert -duration 20s
5768d0b2-0e06-4cb2-9a0a-5e0f0384963d
```
but ..
```
kapacitor define cpu_alert -type stream -tick cpu_usage_idle1.tick -dbrp xinmi_admin.autogen
kapacitor record stream -task cpu_alert -duration 20s
```
no relplay
xinmi_login is olad one which is created several day ago, and xinmi_admin is new one which is created at moment.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with the shown `kapacitor record stream` and `kapacitor define` commands, using `cpu_alert`, `cpu_usage_idle1.tick`, and each database and retention policy. Compare the `xinmi_login.autogen` and `xinmi_admin.autogen` cases and verify what response or replay is expected; done means the cause of the missing response is identified and the recording behaves consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases, stream-processing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100