-
Notifications
You must be signed in to change notification settings - Fork 243
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add monitoring to the docker image #1240
Conversation
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.
My main concern is about the refactoring I did of the profiling in the project and the way to write the doProfile method. Let me know.
Your implementation LGTM, much nicer than before.
@samouri has to review the docker integration
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.
@mathieu-pousse, thank you for the contribution! This looks great. I'll review it later today
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.
Some small nits and comments. Overall this looks fantastic :)
I pushed the fixes I am wondering how does the CI build the image. Will it firstly build the new version of |
We actually don't have a good system for this yet. |
Did I broke the CI with my PR ? Let me know |
Noticed one problem that was causing the optimizer tests to fail. |
And there seems to be another problem that jest fails to init optimizer-docker/metrics.js. One simple fix is to ignore the optimizer-docker dir during tests by adding this to
|
馃帀 |
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.
Awesome - thanks!
As we are now using this docker image in prod, we needed to add some monitoring to understand the overall performances of the project.
Here is the result of what is running in prod for us.
We are able to produce such dashboard to ensure everything is running fine and set alerting on it.
This also helps us to see the most time consuming transformation was the
SeparateKeyframes
that was useless for us and lead me to the previous MR 馃槃BTW, as we are running in k8s, the fact of having metrics exposed will help us to configure an HorizontalPodAutoscaler based on those metrics.
My main concern is about the refactoring I did of the profiling in the project and the way to write the
doProfile
method. Let me know.Hope it helps