You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Colin P. McCabe (JIRA)" <ji...@apache.org> on 2019/05/20 17:21:00 UTC

[jira] [Resolved] (KAFKA-7992) Add a server start time metric

     [ https://issues.apache.org/jira/browse/KAFKA-7992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colin P. McCabe resolved KAFKA-7992.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.3.0

> Add a server start time metric
> ------------------------------
>
>                 Key: KAFKA-7992
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7992
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Stanislav Kozlovski
>            Assignee: Stanislav Kozlovski
>            Priority: Minor
>              Labels: needs-kip
>             Fix For: 2.3.0
>
>
> KIP: KIP-436
> As with all software systems, observability into their health is critical.
> With many deployment platforms (be them custom-built or open-source), tasks like restarting a misbehaving server in a cluster are completely automated. With Kafka, monitoring systems have no definitive source of truth to gauge when a server/client has been started. They are left to either use arbitrary Kafka-specific metrics as a heuristic or the JVM RuntimeMXBean's StartTime, which is not exactly indicative of when the application itself started
> It would be useful to have a metric exposing when the kafka server has started.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)