I'm looking for a tool that might handle this nicely.
I have some asterisk log files that are generated by daemontools' multilog.
The problem is that daemontools rotates logs every few minutes at the
volumes I do so a single call can be scattered across several files. Total
files might be a fe
I've found a small ELK stack reasonable (Kibana is pretty useful for
finding stuff), but needs to be monitored lots (ie, logstash will stop
working for no reason, same with elasticsearch). TBH, splunk is very very
good at this and easy to set up. It *can* be expensive, but if it's worth
money to yo
Op 31 mrt. 2016 12:47 schreef "Simon Lyall" :
>
> I'm looking for a tool that might handle this nicely.
>
> I have some asterisk log files that are generated by daemontools'
multilog. The problem is that daemontools rotates logs every few minutes at
the volumes I do so a single call can be scattere
On 2016-03-31 09:15, Guus Snijders wrote:
> The first thing that comes to mind is grep, with -A and -B (after/before)
> parameters. Not sure how it will perform with such big datasets, but it's
> probably a lot quicker than vi ;).
If you are going to use grep, I strongly suggest that you take a lo
Ditto on Splunk. If you work for a non-profit or education they have a
nice discount.
cheers,
ski
On 03/31/2016 06:43 AM, Graham Dunn wrote:
I've found a small ELK stack reasonable (Kibana is pretty useful for
finding stuff), but needs to be monitored lots (ie, logstash will stop
working for
Big fan of the ELK stack. We're in the process of implementing it here. You
should be able to get the cohesion across files by tagging or custom
fields. It depends on what your source data looks like and I'm not very
familiar with Asterisk or its logs.
Also, don't underestimate the value of using L
As I usually go the straight forward route I would start with grep. I
routinely have to search multiple files and would do
grep "the search string" *filename
The above assumes that the file names are common with maybe a date.
To make things manageable I would do
grep "the search string" *filen
On Thu, Mar 31, 2016 at 11:46:53PM +1300, Simon Lyall wrote:
> I'm looking for a tool that might handle this nicely.
>
> I have some asterisk log files that are generated by daemontools'
> multilog. The problem is that daemontools rotates logs every few
> minutes at the volumes I do so a single ca
> I should have pointed out that, yes, I started with the
> anaconda-ks.cfg from /root after a successful manual install of CentOS 6.6.
>
> And I have that very "lang" line.
FWIW, the anaconda configuration file syntax has steady and
subtly incompatible changes from version to version. Very
easy
On Thu, Mar 31, 2016 at 03:46:53AM PDT, Simon Lyall spake thusly:
> * logstash and Elasticsearch would probably be the longer team option
> although there doesn't seem to be a good built-in asterisk filter for
> grok.
I have been very happy with and have done wonderful things with the ELK
(ela
If one is looking at log aggregation/reporting/alerting systems, I strongly
suggest looking at Graylog. It is (like ELK) built on top of Easticsearch, but
it handles the Elastic management for you. It has a very polished interface and
nice dashboard / alerting features. We’re using it internally
11 matches
Mail list logo
