You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of the feature, modification, idea or suggestion
Recently, we monitored through the cloud console that the Windows virtual machine had insufficient memory. This caused the entire system of the virtual machine to be unable to run normally, and remote desktop login could not be used, making it impossible to locate the specific memory leak process.
Therefore, if we can regularly write the information displayed in the current process list to a file, then when there is insufficient memory in the distribution, we can check the memory usage of the log tracking process, thereby locating the process where the memory leak occurs.
At present, we can only program it ourselves, but obviously the information we collect is not as rich as SI, so if we can directly write the information collected by SI to a file regularly, it will be extremely useful.
thanks
Proposed implementation details (optional)
Maybe it can be implemented as a ui feature, but it will be a lot of work.
Or we can let SI expose some capabilities through cli commands?
The text was updated successfully, but these errors were encountered:
Description of the feature, modification, idea or suggestion
Recently, we monitored through the cloud console that the Windows virtual machine had insufficient memory. This caused the entire system of the virtual machine to be unable to run normally, and remote desktop login could not be used, making it impossible to locate the specific memory leak process.
Therefore, if we can regularly write the information displayed in the current process list to a file, then when there is insufficient memory in the distribution, we can check the memory usage of the log tracking process, thereby locating the process where the memory leak occurs.
At present, we can only program it ourselves, but obviously the information we collect is not as rich as SI, so if we can directly write the information collected by SI to a file regularly, it will be extremely useful.
thanks
Proposed implementation details (optional)
Maybe it can be implemented as a ui feature, but it will be a lot of work.
Or we can let SI expose some capabilities through cli commands?
The text was updated successfully, but these errors were encountered: