I was trying to say you that you don't need to store lots of unnecesary
logs when you can store just the valuable information contained in the
logs, in a processed way.
Why store thousands of log lines that show some called function
functionname1 instead of store something like this:
{
"date"
I tried to do that with syslog-ng but it doesn't work
What exactly didn't work (before writing a longer configuration example)?
It's kind of simple with syslog-ng - you set the nginx log file as source /
provide mysql as destination and that's it.
rr
___
yes, I could do it but I want just store for example the customer, the
function name, the date after with those information I could filter my
report through a page.php
But with json I don't know how can I do that?
2017-04-20 9:57 GMT+02:00 oscaretu . :
> If you extract the lines containing all
If you extract the lines containing all the function names, and filter them
with a script that counts the number of times that the function appears,
you only have to store (for example in a JSON) the number of times that
each function was used. And you can avoid storing all the logs in a
database.
yes, I tried to do that and then I did the analysis with goaccess,
but now I need to do an interface(page.php) for the user can choose
the function that want to filter and then generate a report.
So, I thought put all my information on a database like mysql
2017-04-20 9:11 GMT+02:00 oscaretu . :
Sara, why don't you process the log file just with grep / pcregrep to get
just the lines that containt that function name?
On Thu, Apr 20, 2017 at 9:05 AM, SARA QUISPE MEJIA
wrote:
> I want to parse the log file respect to a client that means to make a
> report of how the client is using my app
I want to parse the log file respect to a client that means to make a
report of how the client is using my application through the information
provided by a log file.
So I need to filter some url where I find an especific name of a function.
For that I thought in insert my log file to database li
nginx does not handle the TCP stack, which is part of the network layer of
the OSI stack, underneath anything nginx does.
Have a look at your OS network stack monitoring tools.
Exhaustion of TCP sockets (or file descriptors) will lead to the
impossibility of opening new connections and might lead
Hi Steve,
Thanks for the reply. How do we determine if there's an overload of tcp
connections via nginx?
Is it via this access logs?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,256026,256036#msg-256036
___
nginx mailing list
nginx@nginx.o
On Sat, 2015-01-10 at 09:50 -0500, exilemirror wrote:
> Hi guys,
>
> I'm new to nginx. Can anyone explain what does - - - "-" "-" "-" "-" -
> means in the access logs? Been getting lots of this in the log file.
> Would like to know if this is the cause of nginx to show that there's a
> spike in t
Hi guys,
I'm new to nginx. Can anyone explain what does - - - "-" "-" "-" "-" -
means in the access logs? Been getting lots of this in the log file.
Would like to know if this is the cause of nginx to show that there's a
spike in traffic through the nginx graph. Example of log below:
[12/Feb/201
11 matches
Mail list logo
