<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic geostats cluster map drilldown: what token/s are available? in Dashboards &amp; Visualizations</title>
    <link>https://community.splunk.com/t5/Dashboards-Visualizations/geostats-cluster-map-drilldown-what-token-s-are-available/m-p/321177#M20662</link>
    <description>&lt;P&gt;I am using the cluster map visualisation and geostats, and I'd like to be able to drilldown on each cluster and show formatted details of all the entities in that area. I can get the raw events for the sourcetype with the default drilldown, but what tokens are available if I want to drill to another dashboard instead? The docs seem to be vague on this point, and the applicable Answers are more than two years old.&lt;BR /&gt;
There seems to be a thing called a geobin which is added to the events in the initial map, but I can see how to generate a useful filter for the target dashboard and panel.&lt;/P&gt;</description>
    <pubDate>Mon, 29 May 2017 13:14:42 GMT</pubDate>
    <dc:creator>cmeo</dc:creator>
    <dc:date>2017-05-29T13:14:42Z</dc:date>
    <item>
      <title>geostats cluster map drilldown: what token/s are available?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/geostats-cluster-map-drilldown-what-token-s-are-available/m-p/321177#M20662</link>
      <description>&lt;P&gt;I am using the cluster map visualisation and geostats, and I'd like to be able to drilldown on each cluster and show formatted details of all the entities in that area. I can get the raw events for the sourcetype with the default drilldown, but what tokens are available if I want to drill to another dashboard instead? The docs seem to be vague on this point, and the applicable Answers are more than two years old.&lt;BR /&gt;
There seems to be a thing called a geobin which is added to the events in the initial map, but I can see how to generate a useful filter for the target dashboard and panel.&lt;/P&gt;</description>
      <pubDate>Mon, 29 May 2017 13:14:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/geostats-cluster-map-drilldown-what-token-s-are-available/m-p/321177#M20662</guid>
      <dc:creator>cmeo</dc:creator>
      <dc:date>2017-05-29T13:14:42Z</dc:date>
    </item>
    <item>
      <title>Re: geostats cluster map drilldown: what token/s are available?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/geostats-cluster-map-drilldown-what-token-s-are-available/m-p/321178#M20663</link>
      <description>&lt;P&gt;@cmeo Predefined tokens for Map can be found at the following Splunk Documentation link.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Viz/PanelreferenceforSimplifiedXML#map_2"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Viz/PanelreferenceforSimplifiedXML#map_2&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 30 May 2017 09:18:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/geostats-cluster-map-drilldown-what-token-s-are-available/m-p/321178#M20663</guid>
      <dc:creator>niketn</dc:creator>
      <dc:date>2017-05-30T09:18:10Z</dc:date>
    </item>
    <item>
      <title>Re: geostats cluster map drilldown: what token/s are available?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/geostats-cluster-map-drilldown-what-token-s-are-available/m-p/321179#M20664</link>
      <description>&lt;P&gt;The docs are fine as far as they go, but the Auto drilldown for the map looks like this:&lt;BR /&gt;
sourcetype=customer  | eval l_location=upper(location) | eval state="VIC" | lookup locations suburb as l_location state output lat lon | search lat&amp;gt;=-35.85938 lat&amp;lt;-35.15625 lon&amp;gt;=143.43750 lon&amp;lt;144.84375&lt;/P&gt;

&lt;P&gt;So it is automatically generating a latitude and longitude range presumably corresponding to the radius of the cluster marker, and supplying this in the search parameters. I cannot see how to pass this range in custom tokens, since the properties of the cluster marker aren't available. The statistics table for the parent map has four fields: geobin, latitude, longitude and a count (of what I'm not sure, not customers certainly) if there's a way to group the lats and longs I don't see it.&lt;BR /&gt;
As an experiment I tried passing $click.lat.value$ into the child dashboard to see what I got, which was exactly one lat value--no range. So, what magic is going on here?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 14:16:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/geostats-cluster-map-drilldown-what-token-s-are-available/m-p/321179#M20664</guid>
      <dc:creator>cmeo</dc:creator>
      <dc:date>2020-09-29T14:16:25Z</dc:date>
    </item>
    <item>
      <title>Re: geostats cluster map drilldown: what token/s are available?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/geostats-cluster-map-drilldown-what-token-s-are-available/m-p/321180#M20665</link>
      <description>&lt;P&gt;You are probably looking for $click.bounds.orientation$. In your example above,&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| search lat&amp;gt;=-35.85938 lat&amp;lt;-35.15625 lon&amp;gt;=143.43750 lon&amp;lt;144.84375
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;the search with tokens would have been&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;| search lat&amp;gt;=$click.bounds.south$ lat&amp;lt;$click.bounds.north$ lon&amp;gt;=$click.bounds.west$ lon&amp;lt;$click.bounds.east$
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;(maybe I've confused east and west there, you might have to check). But this is how you get all events matching the lat/lon bounds produced by the cluster.&lt;/P&gt;</description>
      <pubDate>Tue, 30 May 2017 11:57:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/geostats-cluster-map-drilldown-what-token-s-are-available/m-p/321180#M20665</guid>
      <dc:creator>jeffland</dc:creator>
      <dc:date>2017-05-30T11:57:03Z</dc:date>
    </item>
    <item>
      <title>Re: geostats cluster map drilldown: what token/s are available?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/geostats-cluster-map-drilldown-what-token-s-are-available/m-p/321181#M20666</link>
      <description>&lt;P&gt;OK thanks to the responders, problem solved. Create tokens for the four values passed (N, S, E, W limits) and make sure the target search includes lats and longs. &lt;BR /&gt;
For instance:&lt;BR /&gt;
&lt;CODE&gt;&lt;BR /&gt;
sourcetype=customer| eval l_location=upper(location)|eval state="VIC"&lt;BR /&gt;
          | lookup locations suburb as l_location state output lat lon&lt;BR /&gt;
          | where (lon &amp;gt;= $lon1$ AND lon &amp;lt; $lon2$) AND (lat &amp;gt;= $lat2$ AND lat &amp;lt; $lat1$)&lt;BR /&gt;
          | sort surname1&lt;BR /&gt;&lt;BR /&gt;
          | table firstname1 surname1 phone1 email1 address location&lt;BR /&gt;
&lt;/CODE&gt;&lt;BR /&gt;
And the thing that threw me: I'm in the southern hemisphere, note that the relation operators for lats are reversed because all our lats are negative! Thanks to my good lady wife for spotting that one...D'oh!&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 14:17:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/geostats-cluster-map-drilldown-what-token-s-are-available/m-p/321181#M20666</guid>
      <dc:creator>cmeo</dc:creator>
      <dc:date>2020-09-29T14:17:21Z</dc:date>
    </item>
  </channel>
</rss>

