-
Notifications
You must be signed in to change notification settings - Fork 4
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
SPOT suggesting non-minimal configs and fixed log retriever #62
Conversation
eriklangille
commented
Mar 31, 2022
- Log retriever will fetch more than 50 logs
- Jupyter notebook for data exploration
- All requests saved to collection and deleted when matching request log fetched
- More context to graph; added memory recommendation and fixed polynomial (now displays constant term)
status = res["StatusCode"] | ||
error = False | ||
if status < 200 or status >= 300: | ||
print(f"WARNING: Status code {status} for request id {req_id}") |
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.
What about using the logging
module for warnings
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 understood the request id addition and deletion mechanism to the db. But I couldn't see a followup check utilizing these saved data. Why do we keep this data in the db?
@@ -43,6 +43,10 @@ def __init__( | |||
|
|||
def _preprocess(self): | |||
self._df[MEM_SIZE] = self._df[MEM_SIZE].astype(int) | |||
self._df = self._df[ |
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.
This is quite important addition!
Yeah that part of the code hasn't been properly implemented |