influxdata / influxdata/kapacitor
Kapacitor Recording using HTTP API sets stop time to start of the current minute
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.4k
- Forks
- 479
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 4
Description
==> curl -X POST -d '{"task": "fes", "stop": "2017-01-11T00:05:30Z", "id": "fes_PARSE_ERROR.recording"}' "http://localhost:9092/kapacitor/v1/recordings/stream"
{
"link": {
"rel": "self",
"href": "/kapacitor/v1/recordings/fes_PARSE_ERROR.recording"
},
"id": "fes_PARSE_ERROR.recording",
"type": "stream",
"size": 0,
"date": "2017-01-11T00:05:00.540955435-05:00",
"error": "",
"status": "running",
"progress": 0
}
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 provided curl request against the recordings stream HTTP API and trace how the stop timestamp is parsed or assigned. Done means a recording created with a stop time such as 2017-01-11T00:05:30Z preserves the supplied seconds instead of truncating to the start of the current minute.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100