<?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 Capturing Metrics over TCP using JSON in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Capturing-Metrics-over-TCP-using-JSON/m-p/701372#M116071</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are trying to get metrics into Splunk using TCP, so far we have tried the following:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;inputs.conf&lt;/P&gt;&lt;P&gt;[tcp://44444]&lt;BR /&gt;connection_host = ip&lt;BR /&gt;index = metrics_idx&lt;BR /&gt;sourcetype = "json_no_timestamp" or "_json" or "metrics_csv"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We can get this to work if we change sourcetype to statd and emulate the statd protocol, but we found this to be very limited.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have 30 odd machines collecting "1000s" of data endpoints (mainly counters - was 5 things, now 12) - what would be the best way to get this into Splunk, without using JSON/CSV files...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks !&lt;/P&gt;</description>
    <pubDate>Tue, 08 Oct 2024 22:52:40 GMT</pubDate>
    <dc:creator>dewitp</dc:creator>
    <dc:date>2024-10-08T22:52:40Z</dc:date>
    <item>
      <title>Capturing Metrics over TCP using JSON</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Capturing-Metrics-over-TCP-using-JSON/m-p/701372#M116071</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are trying to get metrics into Splunk using TCP, so far we have tried the following:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;inputs.conf&lt;/P&gt;&lt;P&gt;[tcp://44444]&lt;BR /&gt;connection_host = ip&lt;BR /&gt;index = metrics_idx&lt;BR /&gt;sourcetype = "json_no_timestamp" or "_json" or "metrics_csv"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We can get this to work if we change sourcetype to statd and emulate the statd protocol, but we found this to be very limited.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have 30 odd machines collecting "1000s" of data endpoints (mainly counters - was 5 things, now 12) - what would be the best way to get this into Splunk, without using JSON/CSV files...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks !&lt;/P&gt;</description>
      <pubDate>Tue, 08 Oct 2024 22:52:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Capturing-Metrics-over-TCP-using-JSON/m-p/701372#M116071</guid>
      <dc:creator>dewitp</dc:creator>
      <dc:date>2024-10-08T22:52:40Z</dc:date>
    </item>
    <item>
      <title>Re: Capturing Metrics over TCP using JSON</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Capturing-Metrics-over-TCP-using-JSON/m-p/701376#M116072</link>
      <description>&lt;P&gt;Here is a sample of the data posted to the TCP connection:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;{
"time": 1728428019, "host": "x.x.x.x", "fields":
{
"metric_name:x.x.x.x.ds.bIn": 1111,
"metric_name:x.x.x.x.ds.bOut": 2222
}
}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Oct 2024 22:57:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Capturing-Metrics-over-TCP-using-JSON/m-p/701376#M116072</guid>
      <dc:creator>dewitp</dc:creator>
      <dc:date>2024-10-08T22:57:25Z</dc:date>
    </item>
  </channel>
</rss>

