<?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: Thread Dump &amp;amp; Heap Dump Log Collection in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/What-are-the-possibilities-to-achieve-Thread-Dump-amp-Heap-Dump/m-p/626528#M217760</link>
    <description>&lt;P&gt;You don't ask for "all" possibilities because there are too many, albeit enumerable. &amp;nbsp;The usual way to collect thread dump would be to run kill -3 periodically and just collect JVM logs. (I assume that you really want to collect data at predetermined intervals.) &amp;nbsp;Then, use Splunk to find them. &amp;nbsp;Alternatively, you can run jstack and dump output to files, then use forwarder to collect those files. &amp;nbsp;Alternatively, you can send output to HEC or Splunk API.&lt;/P&gt;&lt;P&gt;To collect heap dump, I assume that you just want histograms, not full object dumps. (The latter is destructive.) &amp;nbsp;One way to do this is to run jmap periodically and dump output to a file, then use forwarder to collect those files. &amp;nbsp;Another way is to run those commands then send output to HEC, or Splunk API.&lt;/P&gt;</description>
    <pubDate>Tue, 10 Jan 2023 08:01:56 GMT</pubDate>
    <dc:creator>yuanliu</dc:creator>
    <dc:date>2023-01-10T08:01:56Z</dc:date>
    <item>
      <title>What are the possibilities to achieve Thread Dump &amp; Heap Dump Log Collection?</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-are-the-possibilities-to-achieve-Thread-Dump-amp-Heap-Dump/m-p/626502#M217751</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;I need to collect "Thread Dump" and "Heap Dump" of the application into Splunk.&amp;nbsp; What are all the possibilities to achieve it?&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jan 2023 16:12:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-are-the-possibilities-to-achieve-Thread-Dump-amp-Heap-Dump/m-p/626502#M217751</guid>
      <dc:creator>ramanan</dc:creator>
      <dc:date>2023-01-11T16:12:17Z</dc:date>
    </item>
    <item>
      <title>Re: Thread Dump &amp; Heap Dump Log Collection</title>
      <link>https://community.splunk.com/t5/Splunk-Search/What-are-the-possibilities-to-achieve-Thread-Dump-amp-Heap-Dump/m-p/626528#M217760</link>
      <description>&lt;P&gt;You don't ask for "all" possibilities because there are too many, albeit enumerable. &amp;nbsp;The usual way to collect thread dump would be to run kill -3 periodically and just collect JVM logs. (I assume that you really want to collect data at predetermined intervals.) &amp;nbsp;Then, use Splunk to find them. &amp;nbsp;Alternatively, you can run jstack and dump output to files, then use forwarder to collect those files. &amp;nbsp;Alternatively, you can send output to HEC or Splunk API.&lt;/P&gt;&lt;P&gt;To collect heap dump, I assume that you just want histograms, not full object dumps. (The latter is destructive.) &amp;nbsp;One way to do this is to run jmap periodically and dump output to a file, then use forwarder to collect those files. &amp;nbsp;Another way is to run those commands then send output to HEC, or Splunk API.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Jan 2023 08:01:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/What-are-the-possibilities-to-achieve-Thread-Dump-amp-Heap-Dump/m-p/626528#M217760</guid>
      <dc:creator>yuanliu</dc:creator>
      <dc:date>2023-01-10T08:01:56Z</dc:date>
    </item>
  </channel>
</rss>

