sexilog icon indicating copy to clipboard operation
sexilog copied to clipboard

vpxd-profiler-* _grokparsefailure tag and some lines commented out

Open Geek2France opened this issue 8 years ago • 0 comments

I use filebeat on windows to ship vpxd-*.log files to logstash. Logstash parse the log files with the filter file "filter-json-vcenter.conf".

I have many log lines with the tag "_grokparsefailure" which means that logstash failed to parse the log.

Examples : This line has not "_grokparsefailure" tag : "--> /VcServiceStats/StartupTime/ServerApp::Start/CustomFieldsManagerMo::Start/numSamples 1"

This line has "_grokparsefailure" tag : "--> /VcServiceStats/StartupTime/ServerApp::Start/CustomFieldsManagerMo::Start/min 28"

I think, this is because you set "break_on_match" to false at line 41. Am i right ?

Other thing, i'm asking me why there are 2 blocks for testing the "OpMoLockStats" pattern. the first block begins at line 45 and the second block begins at line 91.

And finally, why line 62, 64 and 66 are commented out ?

Thank you in advance for your help ! Regards.

Geek2France avatar Jan 10 '17 14:01 Geek2France