fix: update windows recording rules to remove duplicate entries for non running containers #840
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For e.g. The following query returned a many to many matching error:
![image](https://user-images.githubusercontent.com/28612268/233724641-2ce1f075-0dc2-4506-a05f-13b6a109008f.png)
because there where multiple containers within the pod stuck in initizaling state and thus did not have container_id's set:
![image](https://user-images.githubusercontent.com/28612268/233724828-cc954685-fa52-402b-8ee9-3fe67a8ff1e1.png)
Hence our recording rule for them would fail. This fix eliminates those containers which are not running at all as there is no point in getting the cpu/memory usage for them.