Dashboards & Visualizations

Choropleth Sequential Normalisation

WalshyB
Path Finder

Hey Guys,

I have a choropleth map which returns the amount of hits on security data from ip's attacking from different countries

search : index=... | iplocation SRC_IP | stats count by Country | eval count=count | eval Country=if(Country="","unknown",Country) | geom geo_countries featureIdField="Country" | sort + count

The problem is, when searched over a long period of time, the country for the highest has a high count so everything else which has a lot less is put into the lowest bin

e.g. china has 6 million hits so it is in the top bin, whereas everything else has 1m, 500k etc so it is put into the lowest bin.

Is there a way to normalise this so that more colours are shown?

1 Solution

mhpark
Path Finder

Try to

| eval normalizedCount = ln(count)

or something like that, if you can't log scale the map from settings.
or just cut down the China values until you get more colorful maps, I guess.

View solution in original post

mhpark
Path Finder

Try to

| eval normalizedCount = ln(count)

or something like that, if you can't log scale the map from settings.
or just cut down the China values until you get more colorful maps, I guess.

WalshyB
Path Finder

Thanks! Works perfectly 🙂

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

[Puzzles] Solve, Learn, Repeat: Character substitutions with Regular Expressions

This challenge was first posted on Slack #puzzles channelFor BORE at .conf23, we had a puzzle question which ...

Splunk Community Badges!

  Hey everyone! Ready to earn some serious bragging rights in the community? Along with our existing badges ...

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...