<?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 Re: Number of HEC tokens on a Indexer in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/Number-of-HEC-tokens-on-a-Indexer/m-p/490273#M4070</link>
    <description>&lt;P&gt;I think the important consideration is your use case.&lt;BR /&gt;
Whilst you don't hint at what the throughput of these is likely to be, I can't help but think there may be a better way to manage your inbound events.&lt;/P&gt;

&lt;P&gt;As @richgalloway notes, you probably should be running HEC on a heavy forwarder.&lt;BR /&gt;
Any performance impact from a large number of tokens (not something I have ever benchmarked) would be constrained to that server - and not the rest of your deployment.&lt;/P&gt;

&lt;P&gt;That said, if you are expecting a high rate of events (presumably from 500+ sources) you may want to also consider some form of loadbalancing for the HECs.&lt;/P&gt;

&lt;P&gt;Is each token to be mapped to a different sourcetype?&lt;BR /&gt;
If you can add a bit more context (and are happy to do so), you may get some more ideas.&lt;/P&gt;</description>
    <pubDate>Wed, 22 Jan 2020 17:55:24 GMT</pubDate>
    <dc:creator>nickhills</dc:creator>
    <dc:date>2020-01-22T17:55:24Z</dc:date>
    <item>
      <title>Number of HEC tokens on a Indexer</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Number-of-HEC-tokens-on-a-Indexer/m-p/490271#M4068</link>
      <description>&lt;P&gt;Hi there, &lt;BR /&gt;We are going to onboard atleast 500 tokens per Index on a single Indexer. IS there any performance penalty of having these many tokens listening on a single machine.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jun 2020 23:57:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Number-of-HEC-tokens-on-a-Indexer/m-p/490271#M4068</guid>
      <dc:creator>rashi83</dc:creator>
      <dc:date>2020-06-05T23:57:07Z</dc:date>
    </item>
    <item>
      <title>Re: Number of HEC tokens on a Indexer</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Number-of-HEC-tokens-on-a-Indexer/m-p/490272#M4069</link>
      <description>&lt;P&gt;If you have multiple indexers, you should be running HEC on a heavy forwarder.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jan 2020 17:34:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Number-of-HEC-tokens-on-a-Indexer/m-p/490272#M4069</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-01-22T17:34:58Z</dc:date>
    </item>
    <item>
      <title>Re: Number of HEC tokens on a Indexer</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Number-of-HEC-tokens-on-a-Indexer/m-p/490273#M4070</link>
      <description>&lt;P&gt;I think the important consideration is your use case.&lt;BR /&gt;
Whilst you don't hint at what the throughput of these is likely to be, I can't help but think there may be a better way to manage your inbound events.&lt;/P&gt;

&lt;P&gt;As @richgalloway notes, you probably should be running HEC on a heavy forwarder.&lt;BR /&gt;
Any performance impact from a large number of tokens (not something I have ever benchmarked) would be constrained to that server - and not the rest of your deployment.&lt;/P&gt;

&lt;P&gt;That said, if you are expecting a high rate of events (presumably from 500+ sources) you may want to also consider some form of loadbalancing for the HECs.&lt;/P&gt;

&lt;P&gt;Is each token to be mapped to a different sourcetype?&lt;BR /&gt;
If you can add a bit more context (and are happy to do so), you may get some more ideas.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jan 2020 17:55:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Number-of-HEC-tokens-on-a-Indexer/m-p/490273#M4070</guid>
      <dc:creator>nickhills</dc:creator>
      <dc:date>2020-01-22T17:55:24Z</dc:date>
    </item>
  </channel>
</rss>

