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

Delete deprecation log cache when resetting the deprecation logs checkpoint #113635

Closed
cjcenizal opened this issue Oct 1, 2021 · 1 comment
Closed
Assignees
Labels
enhancement New value added to drive a business result Feature:Upgrade Assistant Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more

Comments

@cjcenizal
Copy link
Contributor

ES has implemented a deprecation log cache to reduce noise. It will suppress logs that are duplicates of existing logs. Users expect to see new logs appear after they reset the logging checkpoint, which UA is unable to meet if the log cache is suppressing logs.

To help us fix this problem, the ES team has implemented an API for deleting the log cache in elastic/elasticsearch#78392. We'll consume this API whenever the user resets the checkpoint, to resurface logs that would otherwise have been suppressed.

DELETE on _logging/deprecation_cache
@cjcenizal cjcenizal added enhancement New value added to drive a business result Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more Feature:Upgrade Assistant labels Oct 1, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-stack-management (Team:Stack Management)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:Upgrade Assistant Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Projects
None yet
Development

No branches or pull requests

3 participants