-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Metricbeat collection of ES monitoring data is inconsistent for the license field #14541
Comments
Pinging @elastic/stack-monitoring (Stack monitoring) |
Just tested and this is also happening on @chrisronline Given the impact of this change — Stack Monitoring UI incorrectly showing license as expired — I feel like this should be a blocker for |
@ycombinator I agree. With this bug, any user on a Basic license is not able to use the Stack Monitoring. If a user attempts to load the UI, they will be redirected to a page that shows: |
This was tested on the latest master of each product (ES and beats)
I have a CCS scenario setup with cluster A (prod) and cluster B (
Monitoring
). I have configured metricbeat to collect and ship monitoring data to cluster B. I have configured CCS from cluster A to cluster B.This query:
yields:
Note that there is no
expiry_date_in_millis
field.Then, this query:
yields:
Note the addition of
expiry_date_in_millis: 0
This is causing an issue in Kibana, as our check to see if a license can expire only checks for the presence of the
expiry_date_in_millis
fieldcc @ycombinator
The text was updated successfully, but these errors were encountered: