fluential

It’s Hugo’s terminal theme https://themes.gohugo.io/hugo-theme-terminal/

The way to approach that in logstash is to use fingerprint plugin which can do various formats (including uuids), MURMUR3 seems to be the fastest here.

https://www.elastic.co/guide/en/logstash/current/plugins-fil....

Edit: typo

There would be usually multiple syslog sink servers so there is never a single point of failure. This can be configured in various ways either dns round robin, load balancers or even multiple destinations configured on the client side, rsyslog can iterate over a list in case of failures.

If there is log storm coming from misconfigured app depending on your traffic levels the sink servers should give you a lot of space for an on-call engineer to be notified that something is off and adjust / rate limit / drop accordingly.

Edit: udated with more info

RELP is very much standard syslog wire protocol(which is just plain tcp anyway), but with some extra stuff to avoid losing data. Just fixing tcp issue here, where data could be ACK-ed into OS receive buffer and the app could be killed before offloading into a persisten storage. Not losing data is very important in log shipping.

The json that syslog wraps data in is actually using the same syslog protocol - nothing is chaging here. It's encapsulated within the same protocol. The only reason to unwrap json is when you need to start structuring your data for BI views, your milage may vary. The key is that these two are de-coupled.

Because you work on a basic level networking / storage layers its very easy to reason and build reliable pipelines according to your needs. As you say — you can't beat that.

PS: The pain starts when you need to deal with multiline logs like java stack traces but then you just work with devs to log everything into json.

Edit: split comment, more info

Great article based on real life experience. I have been building logging and protective monitoring pipelines for a while now.

From my experience if it comes to log shipping from hosts rsyslog + relp + disk assited in-memory asynchronous queues are preferred, most of the time you just only have network i/o as logs would not touch disk.

The idea is to ship logs off the device ASAP as well as destination acts as a sink server capable to handle most of the spikes withouth stressing local source. All done via rsyslog which also wraps actual logs into json format locally. The glue could be syslog-tag.

At the other end you could have ELK stack and logstash using json_lines codec input (pretty fast) structuring data further to your likings.

Just looking into metrics now the avg time for logs showing in ELK is 7-200ms (the latency comes mostly from specific reads happening against the ES cluster).

As ELK is always the slowest component, dropping logs compressed in-memory directly onto disk is also an option.

One thing to note is that RELP can produce extra duplicates which are easily handled by inserting into Elasticsearch using specific document ID (some performance penalty) which could be some unique hash computed on (log content, timestamp, host) etc. With this in place you can also easily "replay" stream of logs to fill potential gaps.

This type of setup scales really good as well.

Edit: typos

Rarely such updates are deployed into production without testing in non-prod envs

Looks like „utf8mb4” mysql issue ? :)

You could do port forwarding...

I have had cancelled overall 5 flights during this time for which I got zero response from any airline, there was no option to speak to a human as “all representatives were always busy”. All I could get is a voucher.

I’ve managed to get all refunded 3 x chargeback via credit cards and 2 x paypal. Provided basic proof of purchase. (UK)

Same here + https://addons.mozilla.org/en-GB/firefox/addon/google-search...

You will like this one https://staticman.net/ same concept

The extension idea is really good but is does break some websites plus its really slowing down the browser, after removing it was like a breath of fresh air.

How about Hugo+cms editor on netlify https://www.netlifycms.org/docs/hugo/

Boom egos shaken

Mailbox.org

Worth a read “Explanation of the state of uBlock Origin (and other blockers) for Safari” — https://github.com/el1t/uBlock-Safari/issues/158

Or cookie consent block list https://www.i-dont-care-about-cookies.eu/

I was looking into that space recently and I have used otter.ai for transcriptions which gives you 6000 minutes/month for 8 USD, which is insanely cheap in that space. Their British language model is quite good as well.

I’ve bulk exported generated srt/vtt files from my fav podcasts and using tinysearch that was posted here recently with ableplayer to provide audio full text search of my Jekyll published podcasts posts and with clickable timestamps to audio play of search phrases.

Whenever I want to know what podcaster has to say on specific subject a quick search makes such a difference!

I’ve found any vpn including WireGuard running on mobile draining battery too much.

Disabling third party cookies works much better, and for mobile safari using free ka-block.

After a quick glance, first thing that strikes me is using docker for measuring network bound application performance. Across different versions docker handles networking differently and by default it may have quite significant impact on your results, good example comes from percona guys https://www.percona.com/blog/2016/02/05/measuring-docker-cpu... I wonder what would results be without using docker, or using docker with --net=host

Be aware that very few routers actually have enough power to do openvpn encryption with higher bandwith (20Mbit+) links and 256CBC encryption. You may get better results by downgrading your cipher (not every vpn provider supports that) To achieve good performance you are looking for hardware with Intel QuickAssist, I would recommend putting pfsense on something like http://store.netgate.com/ADI/RCC-VE-2440.aspx

Also relevant - Statistics for Engineers Tutorial at SRECon15 - https://github.com/HeinrichHartmann/StatisticsTutorial

What do you think is the business / legal risk of running few tor relays (no exit) nodes as a commercial company (UK or US based)? One of my friends told me that he would be afraid of the potential of freezing company assets if someone start investigation and those nodes would be part of that case.

Any thoughts? Comments?

One of the best salary negotiation articles I've read: https://news.ycombinator.com/item?id=3501366

"Way of the Superior Man by David Deida"