-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Extract reusable classes from flow metrics #18502
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
Open
andsel
wants to merge
10
commits into
elastic:main
Choose a base branch
from
andsel:fix/extract_resusable_classes_from_flowmetrics
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 8 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
ae0eed1
Introduced common base class to group all kind of data that can be us…
andsel 683e7c5
Extracted flow metric's RetentionWindow in its own class
andsel ad3f56f
Moved selectNewerCapture to newly created DatapointCapture
andsel a9caff4
Fixed method naming
andsel 747e637
Covered type cast with warn log (really unrealistic)
andsel 6208424
Added license header to source code file
andsel b0b0721
Minor, added javadoc comment
andsel 77c8b7a
Fixed bad method renaming
andsel 2b8ca9a
Tried to abstract the RetentionWindow to be just a container of subcl…
andsel 4ceaf14
Minor, fixed synthax
andsel File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
63 changes: 63 additions & 0 deletions
63
logstash-core/src/main/java/org/logstash/instrument/metrics/DatapointCapture.java
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,63 @@ | ||
| /* | ||
| * Licensed to Elasticsearch B.V. under one or more contributor | ||
| * license agreements. See the NOTICE file distributed with | ||
| * this work for additional information regarding copyright | ||
| * ownership. Elasticsearch B.V. licenses this file to you under | ||
| * the Apache License, Version 2.0 (the "License"); you may | ||
| * not use this file except in compliance with the License. | ||
| * You may obtain a copy of the License at | ||
| * | ||
| * http://www.apache.org/licenses/LICENSE-2.0 | ||
| * | ||
| * Unless required by applicable law or agreed to in writing, | ||
| * software distributed under the License is distributed on an | ||
| * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY | ||
| * KIND, either express or implied. See the License for the | ||
| * specific language governing permissions and limitations | ||
| * under the License. | ||
| */ | ||
|
|
||
| package org.logstash.instrument.metrics; | ||
|
|
||
| /** | ||
| * A {@link DatapointCapture} provides access to timing information | ||
| * captured at a specific point in time. | ||
| */ | ||
| abstract class DatapointCapture { | ||
|
|
||
| private final long nanoTime; | ||
|
|
||
| DatapointCapture(final long nanoTime) { | ||
| this.nanoTime = nanoTime; | ||
| } | ||
|
|
||
| /** | ||
| * @return the nanoTime of this capture, as provided at time | ||
| * of capture by the {@link FlowMetric}. | ||
| */ | ||
| public long nanoTime() { | ||
| return nanoTime; | ||
| } | ||
|
|
||
| /** | ||
| * Internal tooling to select the younger capture between and this and proposed. | ||
| */ | ||
| DatapointCapture selectNewestCapture(final DatapointCapture proposed) { | ||
| if (proposed == null) { | ||
| return this; | ||
| } | ||
|
|
||
| return (this.nanoTime() > proposed.nanoTime()) ? this : proposed; | ||
| } | ||
|
|
||
| /** | ||
| * Internal tooling to select the younger of two captures provided. | ||
| */ | ||
| static DatapointCapture selectNewestCaptureOf(final DatapointCapture existing, final DatapointCapture proposed) { | ||
| if (existing == null) { | ||
| return proposed; | ||
| } | ||
|
|
||
| return existing.selectNewestCapture(proposed); | ||
| } | ||
| } |
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I' not sure exactly what the right abstraction is, but needing to use
instanceofhere in the middle of this chain whenFlowCaptureis the only concrete implementation ofDatapointCapturefeels like we're setting ourselves up for leaky encapsulation.The logic here (mapping retention windows to values) is very tightly-coupled with the nature of flow metrics, which as rate-of-change metrics relies pretty heavily on the baseline/comparison shortcuts, while I know that the proposed histogram metrics won't be using. I took a pretty big stab at generalizing this a few months ago (to make supporting your histogram work possible), but was unable at the time to find an abstraction that actually encapsulates both. While there are certainly parallels between the two, the implementation details of flow metrics clash with those of the histograms.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understand your point, so I would circle back on the meaning of the retention window. The retention window is a concurrent list of datapoints, so I imagined it as container of those. The characteristic of datapoints is that are values of measures taken at a specific time, so that compaction and expiration logic (drop and remove from the list) can be applied.
If we move some aggregation logic specific to flow metric or histogram computation outside of the container then we could get a reusable data structure. For example, FlowMetric uses the
baselinewhile the HdrHistogramFlowMetric in #18503 leverage an iteration methodforEachCapture. If we move these logic outside in a class that has responsibility to compute something out of raw data, then we could reuse the code. WDYT?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With 2b8ca9a I tried to make
RetentionWindowa container of subclasses of DatapointCapture. Now theExtendedFlowMetricdeclare to useRetentionWindows ofFlowCaptures and with this spirit in #18503 theHistogramSnapshotsWindowwill declare to useRetentionWindowofHistogramCapture. In that PR theforEachCapturewill remain in theRetentionWindowas legit way to iterate over the data points, unless we decide thatRetentionWindowis anIterable.