Loading Profile...
Debug output to see where its at in parsing a logfile?
This looks like a really great tool! I'm wondering how to get around a few limitations in the current release.
Is there a way to have a debug output or other way to see where in the input file Spike is at while its loading the logfile? It seems to be getting hung somewhere along the line.
Any idea how big a log file it can cope with? I have a 176M File that it seems to be choking on.
Is there a way to have a debug output or other way to see where in the input file Spike is at while its loading the logfile? It seems to be getting hung somewhere along the line.
Any idea how big a log file it can cope with? I have a 176M File that it seems to be choking on.
I’m liking this program
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi Robert.
You raise some very good points which, alas, I don't have very good answers to right now.
I've loaded similar size log files in the past and it's slow but it will load them - unless something goes wrong.
The parser is really crap. Apparently I've yet to learn the lesson that every time I think "This is simple, I can hand-roll this parser" I should slap myself and sit down with Ragel.
The only thing I can say in my defence is that the source is available so someone with more time & inclination can fork and fix these problems.
Realistically I don't see myself having time to do so in the near future.
Regards,
Matt
EMPLOYEE
