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

Add custom timeInTopic metric to timeseries-aggregator #172

Merged
merged 6 commits into from
Nov 30, 2018

Conversation

JordanJLopez
Copy link
Contributor

This PR adds a new metric that measures the amount of time between a given span's creation timestamp and the point at which it is consumed as part of trends creation.

Our goal is to be able to demonstrate the amount of time between the time an app submits a trace and the time it takes to generate trends off of it is underneath a certain upper bound.

@codecov-io
Copy link

codecov-io commented Nov 28, 2018

Codecov Report

❗ No coverage uploaded for pull request base (master@c349df4). Click here to learn what that means.
The diff coverage is 0%.

Impacted file tree graph

@@           Coverage Diff           @@
##             master   #172   +/-   ##
=======================================
  Coverage          ?     0%           
=======================================
  Files             ?     30           
  Lines             ?     36           
  Branches          ?      6           
=======================================
  Hits              ?      0           
  Misses            ?     36           
  Partials          ?      0
Impacted Files Coverage Δ
...w/haystack/trends/aggregation/WindowedMetric.scala 0% <0%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c349df4...6ed9a5d. Read the comment docs.

@@ -52,6 +53,8 @@ class WindowedMetric private(var windowedMetricsMap: mutable.TreeMap[TimeWindow,
* @param incomingMetricData - incoming metric data
*/
def compute(incomingMetricData: MetricData): Unit = {
timeInTopicMetricPointHistogram.update(incomingMetricData.getTimestamp() - System.currentTimeMillis())
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is incomingMetricData.getTimestamp() is in micros?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You know, I'm not sure, let me double check

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll update my PR with that info

@ashishagg ashishagg merged commit 56f03c6 into ExpediaDotCom:master Nov 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants