Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update observability to report on and use the build number log #171739

Open
Tracked by #170421
jloleysens opened this issue Nov 22, 2023 · 2 comments
Open
Tracked by #170421

Update observability to report on and use the build number log #171739

jloleysens opened this issue Nov 22, 2023 · 2 comments
Assignees
Labels
blocked Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@jloleysens
Copy link
Contributor

jloleysens commented Nov 22, 2023

We want to be able to know when older Kibana UI builds reach our Kibana server to help inform when it is OK to:

  • generally know that old clients are still in use
  • remove old, internal API versions

Note: this would be a step beyond just logging when an error happens as this is more of a passive observation that any old UI client has reached Kibana server.

@jloleysens jloleysens self-assigned this Nov 22, 2023
@botelastic botelastic bot added the needs-team Issues missing a team label label Nov 22, 2023
@jloleysens jloleysens added the Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc label Nov 22, 2023
@botelastic botelastic bot removed the needs-team Issues missing a team label label Nov 22, 2023
@jloleysens
Copy link
Contributor Author

Regarding removing old internal API versions, the Core team is proposing a different approach to start with:

When deleting an API version from Kibana code we should give it a sunset of 30d. This almost eliminates the possibility that an old client can still be in use because of the global session timeouts in place: users must refresh authentication tokens which requires a refresh of the Kibana client also.

@jloleysens
Copy link
Contributor Author

It's likely the case that we want to log build numbers in our proxy logs if we want to address this comprehensively. Blocking this issue until we have sufficient justification to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

No branches or pull requests

1 participant