Visualizing the Donors Choose data set with Kibana and Elasticsearch

The Elasticsearch example codebase includes a Donors Choose public data set. The example uses a set of Kibana visualizations. The following image shows a subset of the visualizations used in the dashboard.  

Donors Choose Kibana Dashboard

  • The map visualization uses provided geopoint , Lat and Long, data.
  • You can see there are 
    • 6.2 million donations in the data set.
    • 2 million donations.
    • $500 million in donated
    • Contains data from 2003 through 2018

Video Talk

This talk mostly describes how to get the data set and index it in Elasticsearch and then visualize with the provided dashboard.

Importing the Dashboard

This assumes that you have already indexed the data using the scripts in the GitHub repository. See the related blog pieces for more information.

Connect to the Kibana dashboard.  If you ran Elasticsearch / Kibana locally then the URL is probably:
  • http://localhost:5601
Verify the index exists.  You can explore the fields by clicking on donorschoose
Visualizations bind to index patterns.  Create an index pattern using the new index.
First specify the pattern value you will use to bind to the index
Specify the field to be used for the time series. All Elasticsearch data is time series data.

You should be presented with the fields that make up the donorschoose index pattern fields
The index pattern donorschoose should now appear in the Saved Objects list
Now we are going to load the saved dashboard configuration.  Load donorschoose_dashboard.ndjson from the git repository
The Index Pattern Identifier will have changed so we need to tell the loaded items that they are bound to the index pattern we created above.  Make sure you do this for any/all that are pointed out in the right side panel.  Select donorschoose for any index pattern binding requests.
The dashboard consists of a Dashboard parent and 30+ visualizations. Find and click on the Dashboard parent to launch a connection to the dashboard.

Tha's all folks. You should now see a visualization similar to the one at the top of the blog. Set the date range to start in 2003.

Blogs in this set

Comments

Post a Comment

Popular posts from this blog

Accelerate Storage Spaces with SSDs in Windows 10 Storage Pool tiers

Image
Create Storage Spaces in Windows 10 Windows Server O/S contains Storage Spaces support for Server Spaces tiered storage. You can front slower spinning disks with smaller faster SSDs. Windows 10 has a Storage Spaces GUI Control Panel that does not include the tiered storage GUI. This means Powershell must be used for all configuration. https://github.com/freemansoft/win10-storage-spaces  contains scripts that create tiered storage pools that integrate SSDs as caching drives and HDDs as storage drives. They assume you have at least one SSD and one HDD. The scripts automatically find all raw drives and add them to the pool. Some HDDs have their types incorrectly identified. The script can coerce them to be MediaType:HDD The entire virtual drive is added to the system as a single large volume You need at least 1 SSD and 1 HDD to run cached storage / Simple resiliency 2 SSD and 2 HDD to run cached storage / Mirror resiliency / 1 SSD and 2 HDD to run cached storage / Simple re
Read more

Java 8 development on Linux/WSL with Visual Studio Code on Windows 10

Image
Linux on Windows via WSL 2, has become a great development environment when targeting cloud containers and functions.  Windows has a shot at becoming the favorite desktop for users building Linux applications. Visual Studio Code (VSCode) is a great IDE. VSCode can run in a split GUI/Server fashion with the GUI in Windows and all the full SDLC executing on Linux. Development happens inside the Linux, WSL2 leveraging VS Code Server The GUI happens as a real part of the Windows Desktop and connects to Remote  VSCode servers, in this case in WSL Linux Ooh A Video Java Development VSCode's Java integration is built on top of Java 11.  This means you probably will end up with Java 11 JDK installed in WSL2 Linux and in Windows.  By default, applications will be Compiled with Java 11.   You can target  application compilation against versions other than the one used by the IDE. This is done by installing the needed Java versions on the Linux side and adding the Java installation locations
Read more

Understanding your WSL2 RAM and swap - Changing the default 50%-25%

Image
The Windows Subsystem for Linux operates as a virtual machine that can dynamically grow the amount of RAM to a maximum set at startup time.  Microsoft sets a default maximum RAM available to 50% of the physical memory and a swap-space that is 1/4 of the maximum WSL RAM.  You can scale those numbers up or down to allocate more or less RAM to the Linux instance. The first drawing shows the default WSL memory and swap space sizing. The images below show a developer machine that is running a dev environment in WSL2 and Docker Desktop.  Docker Desktop has two of its own WSL modules that need to be accounted for.  You can see that the memory would actually be oversubscribed, 3 x 50% if every VM used its maximum memory.  The actual amount of memory used is significantly smaller allowing every piece to fit. Click to Enlarge The second drawing shows the memory allocation on my 64GB laptop. WSL Linux defaults to a maximum RAM size of 5
Read more