You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We automatically show deployment annotations based on service.version if the user is not using the API. The logic is as follows:
get all the values for service.version in the given time range
if there is more than one, fetch the oldest document (not by the given time range) for each value of service.version: "first seen"
display an annotation at/if its "first seen" timestamp is within the given time range.
However, in #92112, I changed the min aggregation to fetch + sorting on @timestamp. Unfortunately I used descending instead of ascending, which results in the annotation almost always being displayed, because it uses the last seen instead of the first seen, as reported by @LucaWintergerst.
The text was updated successfully, but these errors were encountered:
Adding some context to what this looks like and when it happens. When running a service with two different versions, two annotations will be displayed at the end of the chart when the last event for each respective service happened. It will keep happening until the current time window only has data from one service version.
We automatically show deployment annotations based on
service.version
if the user is not using the API. The logic is as follows:service.version
in the given time rangeservice.version
: "first seen"However, in #92112, I changed the
min
aggregation to fetch + sorting on @timestamp. Unfortunately I used descending instead of ascending, which results in the annotation almost always being displayed, because it uses the last seen instead of the first seen, as reported by @LucaWintergerst.The text was updated successfully, but these errors were encountered: