8000 Metrics for fleet daemon via Prometheus · Issue #1233 · coreos/fleet · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
This repository was archived by the owner on Jan 30, 2020. It is now read-only.
This repository was archived by the owner on Jan 30, 2020. It is now read-only.
Metrics for fleet daemon via Prometheus #1233
Closed
@mwitkow

Description

@mwitkow

Etcdv2 seems to have preliminary support for Prometheus metrics (2.1alpha). Are you guys planning on adding support for Prometheus metrics as well? It would be fantastic to be able to monitor:

  • whether this fleet instance is the current engine leader
  • task completion broken down by:
    • outcome (success, failure)
    • failure reason code, e.g. machine_left_cluster
  • number of locally scheduled fleet tasks (on that instance)
  • number of machines in the cluster by tag string

If it's not on your roadmap anytime soon, can you provide pointers on how to start hacking on this?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0