awslogs VS GoAccess

Using the official CLI (aws logs get-log-events) or https://github.com/jorgebastida/awslogs is pretty close to SSH-ing and grepping.

cw is a native executable targeting your OS, and not needed external dependencies such as pip and npm. Compared to awslogs which is famous helpful tool for CloudWatch Logs1, cw is written in golang and faster.

Its a command line tool but some people I know also use awslogs

Not a full solution, but when I was doing this I really got to love the awslogs utility:

https://github.com/jorgebastida/awslogs

It allows you to stream Cloudwatch logs from the command line, so you can grep them, save them to files, etc... (The web based Cloudwatch interface is terrible.)

Another suggestion is to try to modularize the core business logic in your lambda such that you separate the lambda-centric stuff from the rest of it. Obviously, though, if "the rest of it" is hitting other AWS services, you're going to hit the same testing roadblock.

Or you can try mocking, which may or may not provide much value for you. There's a python library for that, (moto), but it's not 100% up to date wrt AWS services/interfaces, last I had checked. Might be worth a try though.

https://github.com/spulec/moto

Cloudwatch Logs is pretty meh visually, but awslogs can give you a pretty good `tail -f`-like experience, and Insights is pretty good. Cloudwatch Metric Filters give you a 'StatsD'-like experience, in that you can log out a certain message or code and then use its appearance as a metric.

Check out https://github.com/jorgebastida/awslogs , you can define a `--start`, and it also has a `--watch`, and can be piped the `grep` or whatever you want. It's a pretty flexible tool.

📖 awslogs - a simple command-line tool for querying groups, streams, and events from Amazon CloudWatch logs.

If one wants server-side metrics with a little more info than the author's "hacky little script", there's always goaccess [1], which functions in broadly the same way. I even use it with Firebase Hosting-hosted sites via [2] (which I wrote).

[1] http://goaccess.io/

[2] https://github.com/Silicon-Ally/gcp-clf

> Just use GoAcces for fuck's sake.

GoAccess seems pretty cool and is probably a good task for the job, when you need something simple, thanks for recommending it: https://goaccess.io/

Even if you have analytics of some sort already in place, I think it'd probably still be a nice idea to run GoAccess on your server, behind some additional auth, so you can check up on how the web servers are performing.

That said, I'd still say that the analytics solutions out there, especially self-hostable ones like Matomo, are quite nice and can have both UIs that are very easy to interact with for the average person (e.g. filtering data by date range, or by page/view that was interacted with), as well as have a plethora of different datasets: https://matomo.org/features/

I think it can be useful to have a look at what sorts of devices are mostly being used to interact with your site, what operating systems and browsers are in use, how people navigate through the site, where do they enter the site from and how they find it, what the front end performance is like, or even how your e-commerce site is doing, at a glance, in addition to seeing how this changes over time.

People have also said good things about Plausible Analytics as well: https://plausible.io/

Maybe, if it's just local and need just information, maybe https://goaccess.io is an option.

I run goaccess on a cron job and have paired it with a MaxMind GeoIP database so that you can see where people are coming from etc.

https://goaccess.io/

file on GitHub.

There is small programm for linux https://goaccess.io/

I heard about https://goaccess.io/ (and even tested it) but first, nothing about tracing logs, and I think that the provided HTML dashboard isn't enough security-oriented for me but it's more about monitoring your customer volume... It does -partially- fit my case.

Loved AWStats! Still can be useful — but bots, client side caching, CDNs, and did I mention bots..? have made the data hard to rely on for much. A while ago I switched from AWStats to GoAccess (https://goaccess.io/) for this kind of thing. I prefer its interface, and it's way way faster to churn through big log files (C vs. Perl).

matomo and goatcounter are nice, but there are even solutions which don't need any extra CPU or any extra client request:

• https://goaccess.io/

• https://www.awstats.org/

Both of them are free/open-source.

GoAccess is a powerful web log analyzer that generates real-time web traffic statistics.