-
Notifications
You must be signed in to change notification settings - Fork 631
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
feat(signalfx): Provide additional context about the results of the signalflow programs. #617
feat(signalfx): Provide additional context about the results of the signalflow programs. #617
Conversation
…ignalflow programs.
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.
💯 looks good to me!
@@ -56,6 +56,16 @@ | |||
@Slf4j | |||
public class SignalFxMetricsService implements MetricsService { | |||
|
|||
private static final String SIGNAL_FLOW_ERROR_TEMPLATE = | |||
"An error occurred whole executing the Signal Flow program. " |
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.
typo: whole
-> while
?
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.
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.
Looks good, minus the typo in the error message template
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.
Sorry for the late review. LGTM2.
We noticed that in Signal Fx if you have metrics that are reporting at differing frequencies.
Say a system agent on an EC2 instance that reports system cpu and memory at 1 data point per minute and application metrics that report 6 times per minute.
In Kayenta if you set the step to 10 (6 datapoints per minute) that the CPU and Memory data gets padded with a bunch of NaNs and gets graphed weird.
Just taking that data and stretching it had some side effects as well, so this PR adds more attributes to the data that flows through with the results so that the data can be reconstructed and graphed more accurately.
Before:
After:
CC: @melanahammel