Skip to content
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

Install failed because of code inside go-homedir missed, could you kindly help to check #3

Open
pencui opened this issue May 22, 2016 · 6 comments
Assignees
Labels

Comments

@pencui
Copy link

pencui commented May 22, 2016

$ go get github.com/gophergala2016/Pulse/LogPulse
work\src\github.com\gophergala2016\Pulse\LogPulse\config\config.go:9:2: no build
able Go source files in C:\work\src\github.com\mitchellh\go-homedir

@dixonwille
Copy link
Contributor

I am on a short vacation until tomorrow. I will check it out then. Thanks.

@dixonwille
Copy link
Contributor

dixonwille commented May 27, 2016

@pencui go get is not seeming to get github.com\mitchellh\go-homedir try running
$ go get github.com/mitchellh/go-homedir
first then running
$ go get github.com/gophergala2016/Pulse/LogPulse

@dixonwille
Copy link
Contributor

Also LogPulse itself is an executable so a go install github.com/gophergala2016/Pulse/LogPulse may be preferable. The "brain of the project" is github.com/gophergala2016/Pulse/pulse

@dixonwille dixonwille self-assigned this May 27, 2016
@dixonwille
Copy link
Contributor

Please let me know if this works for you!

@pencui
Copy link
Author

pencui commented May 28, 2016

Hi,
Yes, It works, but why the log parsing result is all normal logs with "info" level, all "error" level was ignored. Just like this:

LogPulse.exe syslog

{"message":"Alert! Found Anomaly in Log Files via LogPulse","body":"Dec 27 16:37:33.271012 info CLA-0 fmpprb: RU:OMU-0|PNAME:IL_Fmpprb|LPID:16944|PID:0x677 N/A N/A|TIME:2014-12-27 16:37:33:270961|TEXT:fmpprb callback is called, feature code:0000000104,lic_state 0|DATA:"}
{"message":"Alert! Found Anomaly in Log Files via LogPulse","body":"Dec 27 16:37:33.460670 info CLA-1 HASClusterManag[3748]: INFO StartupController: Allowing startup of /CLA-0/OMUTestServer-0 with role ACTIVE (ongoing = 1, waiting = 26, loadFactor = 10%)"}

I checked with the log kern.log.2, it did filtered lots of abnormal logs. Is there something wrong I use this
script? Or what kind of log, can use this tool to find out abnormal logs? thanks.

Br
Pencui

@dixonwille
Copy link
Contributor

The more you feed it the more it learns. It does not get trained, and finds its own pattern. You are using it correctly and this was a project built on 48 hours. I would not believe in the results too much but rather the concept. The way I see it those info logs could be what caused an error?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants