David Ashpole
0995283c32
Merge pull request #2160 from gaorong/victimContainerName
...
change default oom victim container name
2019-02-05 09:27:02 -08:00
gaorong
1ea111582c
cleanup oom parser test
2019-02-02 10:08:58 +08:00
gaorong
407289527c
change default oom victim container name
2019-02-02 10:00:57 +08:00
Euan Kemp
95f9c8c86f
oomparser: update to use kmsg based parser
...
This provides much more robust support for kernel logs via accessing the
`/dev/kmsg` interface to them directly.
2017-08-30 15:35:40 -07:00
Euan Kemp
fe722c7b02
oomparser: don't get stuck for certain processes
...
The oomparser logic would end up stuck, unable to detect the end of a
given oom trace, for any process with a name that didn't match \w+.
This includes processes like 'python3.4' due to the '.', or
'docker-containerd' due to the '-'.
This fix was included in pr #1544 last year, but since that PR seems
dead it seems like a good idea to break this more important fix out.
I've updated the tests such that they would have caught this issue.
2017-08-01 16:21:31 -07:00
Euan Kemp
125d026aae
oomparser: Fix tests
...
They had reflect.Equal instead of !reflect.Equal.
They also depended on the current year. Which changed.
2016-10-20 10:50:14 -07:00
Phillip Wittrock
dee3f07b0a
resolves #1030 oomparser_test should get the current year for matching the time of death.
2016-01-04 10:50:08 -08:00
Victor Marmol
32b33b215a
Add support for identifying OOM victim.
2015-04-15 13:09:22 -07:00
Katie Knister
21e96ed61c
adding systemd oomparser functionality
2015-03-24 12:33:57 -07:00
Katie Knister
78f3029943
Fixed some bugs in oomparser streaming
2015-03-10 18:18:54 -07:00
Katie Knister
412f27798e
Revised oomparser to not use all the cpu
2015-03-02 14:22:53 -08:00
Katie Knister
1291347c73
small change to the way time is parsed from the kernel log in oomparser
...
small change to the way time is parsed from the kernel log in oomparser
2015-02-04 18:48:34 -08:00
Katie Knister
c806d603ba
Added a test file for oomparser
2015-01-30 10:24:08 -08:00
