The client I work for at this time is leveraging Axon 3. The events are stored in a PostgreSQL database. PostgreSQL uses a thing called TOAST (The Oversized-Attribute Storage Technique) to store large values. From the PostgreSQL documentation: “PostgreSQL uses a fixed page size (commonly 8 kB), and does not allow tuples to span multiple […]
You are browsing archives for
Author: Patrick Kik
Kibana Histogram on Day of Week
I keep track of my daily commutes to and from the office. One thing I want to know is how the different days of the week are affecting my travel duration. But when indexing all my commutes into Elasticsearch, I can not (out-of-the-box) create a histogram on the day of the week. My first visualization […]
Simulating an Elasticsearch Ingest Node pipeline
Indexing document into your cluster can be done in a couple of ways: using Logstash to read your source and send documents to your cluster; using Filebeat to read a log file, send documents to Kafka, let Logstash connect to Kafka and transform the log event and then send those documents to your cluster; using […]
Public Elasticsearch clusters are being held ransom
Last week several news sites and researchers reported that Elasticsearch clusters that are connected to the internet without proper security are being held ransom. You can use shodan.io to search for Elasticsearch clusters: https://www.shodan.io/search?query=port%3A9200+json&language=en. The first hit is actually a cluster that is ‘infected’: There are some secured clusters as well: But the default ‘root’ account with […]
Elastic{ON} 2016
Last week a colleague and I attended Elastic{ON} in San Francisco. The venue at Pier 48 gave a nice view on (among others) the Oakland Bay Bridge. Almost 2000 Elastic fanatics converged to listen to and talk about everything in the Elastic Stack. I have been to a lot of sessions. I think the two […]
Shield your Kibana dashboards
You work with sensitive data in Elasticsearch indices that you do not want everyone to see in their Kibana dashboards. Like a hospital with patient names. You could give each department their own Elasticsearch cluster in order to prevent all departments to see the patient’s names, for example. But wouldn’t it be great if there […]