Answers: <p>Based on community answer to that question it turned out there isn't count of the seconds, it is count of all samples for given histogram.
  That means I had ~146,000 HTTP connections to that API server in that period.</p>
  
Answers: CC BY-SA 4.0
Answers: 2020-06-08T12:00:31.250Z
Answers: 2020-06-08T12:00:31.250Z
Answers: anVzdGFub3RoZXJodW1hbg
Body: <p>In the 2 pictures below I am comparing the metric from K8s apiserver_client_certificate_expiration_seconds_count{job="apiserver"} for my 3 master nodes on K8s 1.14.3. A single day should have 86400 seconds, how come at the start of the day for a given node Prometheus displays 59565 at 00:00 and at 24:00 it shows 205534 seconds? Does that mean that the metric reported by k8s is broken or my query on the graphical dashboard has something in it that I don't understand? In theory it should mean that many seconds have expired from the api server cert, but the math doesn't match the specifications?
  <a href="https://i.sstatic.net/jbLAQ.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/jbLAQ.png" alt="enter image description here"></a></p>
  
  <p><a href="https://i.sstatic.net/oYMVy.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/oYMVy.png" alt="enter image description here"></a></p>
  
Tags: <prometheus>
Title: K8s to Prometheus apiserver_client_certificate_expiration_seconds_count metric, why does it count more seconds than 86400 for a single day?
UserDisplayName: anVzdGFub3RoZXJodW1hbg
ThreadText: # K8s to Prometheus apiserver_client_certificate_expiration_seconds_count metric, why does it count more seconds than 86400 for a single day?
  
  (Asked by: username_0 on 2020-06-04)
  
  In the 2 pictures below I am comparing the metric from K8s apiserver\_client\_certificate\_expiration\_seconds\_count{job="apiserver"} for my 3 master nodes on K8s 1.14.3. A single day should have 86400 seconds, how come at the start of the day for a given node Prometheus displays 59565 at 00:00 and at 24:00 it shows 205534 seconds? Does that mean that the metric reported by k8s is broken or my query on the graphical dashboard has something in it that I don't understand? In theory it should mean that many seconds have expired from the api server cert, but the math doesn't match the specifications?
  [![enter image description here](https://i.sstatic.net/jbLAQ.png)](https://i.sstatic.net/jbLAQ.png)
  
  [![enter image description here](https://i.sstatic.net/oYMVy.png)](https://i.sstatic.net/oYMVy.png)
  
  **Tags:** prometheus
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2020-06-08. Score: 0 | Accepted answer
  
  Based on community answer to that question it turned out there isn't count of the seconds, it is count of all samples for given histogram.
  That means I had ~146,000 HTTP connections to that API server in that period.
  
  
  ---
  
  