Expose metrics for Actions
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
(this is still a little brainstormy)
Our metrics reference should include some metrics that come from Nomad Actions.
The current closest related metric appears to be nomad.nomad.alloc.exec which shows time to establish exec, and isn't really what we want here (it's a server metric).
Some ideas for things we might want to expose as allocation metrics:
-
nomad.client.allocs.actions.running
Might give us output like:
{
"Labels": {
"task_group": "group1",
"alloc_id": "2a30175d-c557-82ee-ef04-dc2c615d5112",
"task": "task",
"namespace": "default",
"host": "philrenaud-QM4916XLLX",
"job": "actions-demo-service"
},
"Name": "nomad.client.allocs.actions.running",
"Value": 1
},
-
nomad.client.allocs.actions.failed -
nomad.client.allocs.actions.complete
Contributor guide
No contributing guide indexed for this repository
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 with the metrics reference and the existing nomad.nomad.alloc.exec metric described in the issue. Clarify the semantics and implementation scope for running, failed, and complete allocation-action metrics; done requires an agreed design and corresponding metrics documented in the reference.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100