Repository navigation
[Uptime] Add certificate expiration dates to uptime GQL schema - #43352
Merged
Merged
Conversation
Contributor
|
Pinging @elastic/uptime |
Contributor
💔 Build Failed |
Contributor
💚 Build Succeeded |
Contributor
💚 Build Succeeded |
andrewvc
requested changes
Aug 30, 2019
andrewvc
left a comment
Contributor
There was a problem hiding this comment.
This generally looks good, but is there a reason the indentation on the scripted metric query was changed? Did the formatter do that?
justinkambic
added a commit
to justinkambic/kibana
that referenced
this pull request
Sep 10, 2019
…ic#43352) * Add certificate expiration date to uptime GQL schema. * Update test fixture/snapshot for broken unit test.
justinkambic
added a commit
that referenced
this pull request
Sep 12, 2019
… (#45221) * Add certificate expiration date to uptime GQL schema. * Update test fixture/snapshot for broken unit test.
Contributor
Author
patrykkopycinski
pushed a commit
to patrykkopycinski/kibana
that referenced
this pull request
May 6, 2026
…ic#43352) * Add certificate expiration date to uptime GQL schema. * Update test fixture/snapshot for broken unit test.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The purpose of this patch is to add TLS certificate expiration date/time to our GraphQL schema.
We can now get this information in a format like:
{ "state": { "monitor": { "name": "elastic-website" }, "tls": { "certificate_not_valid_after": [ "2020-07-16T03:15:39.000Z" ] } } }Testing this PR
{ getMonitorStates(dateRangeStart: "now-15m", dateRangeEnd: "now") { summaries { state { monitor { name } tls { certificate_not_valid_after } } } } }