<?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: Logging to SPLUNK from a JMP script in Discussions</title>
    <link>https://community.jmp.com/t5/Discussions/Logging-to-SPLUNK-from-a-JMP-script/m-p/950861#M109873</link>
    <description>&lt;P&gt;At least in our SPLUNK instance the separator between Name and VALUE is a colon.&amp;nbsp; So,&amp;nbsp;&lt;BR /&gt;"event" =&amp;gt; "Test message"&lt;/P&gt;
&lt;P&gt;becomes&lt;/P&gt;
&lt;P&gt;"event" : "Test message"&lt;/P&gt;</description>
    <pubDate>Wed, 27 May 2026 16:00:33 GMT</pubDate>
    <dc:creator>RC_Flyer</dc:creator>
    <dc:date>2026-05-27T16:00:33Z</dc:date>
    <item>
      <title>Logging to SPLUNK from a JMP script</title>
      <link>https://community.jmp.com/t5/Discussions/Logging-to-SPLUNK-from-a-JMP-script/m-p/949207#M109805</link>
      <description>&lt;P&gt;Has anyone written JSL to send messages to a SPLUNK instance?&amp;nbsp; The idea would be to capture all of the log messages from multiple applications in a single spot&lt;/P&gt;</description>
      <pubDate>Tue, 19 May 2026 11:06:26 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Logging-to-SPLUNK-from-a-JMP-script/m-p/949207#M109805</guid>
      <dc:creator>RC_Flyer</dc:creator>
      <dc:date>2026-05-19T11:06:26Z</dc:date>
    </item>
    <item>
      <title>Re: Logging to SPLUNK from a JMP script</title>
      <link>https://community.jmp.com/t5/Discussions/Logging-to-SPLUNK-from-a-JMP-script/m-p/949650#M109822</link>
      <description>&lt;P&gt;I've not used splunk but the idea of central logging is a good one. It does look easy enough to send data to splunk once the server is set up.&amp;nbsp; This is not tested, but something close to this should do the trick:&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-jsl"&gt;New HTTP Request(
	URL( "https://your-hostname:8088/services/collector" ),
	Method( "POST" ),
	Headers([
		"Accept" =&amp;gt; "application/json",
		"Authorization" =&amp;gt; "Splunk your-hec-token"
	]),
	JSON([
		"event" =&amp;gt; "Test message",
		"sourcetype" =&amp;gt; "jmp/jsl"
	])
) &amp;lt;&amp;lt; Send;&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 21 May 2026 03:11:08 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Logging-to-SPLUNK-from-a-JMP-script/m-p/949650#M109822</guid>
      <dc:creator>ih</dc:creator>
      <dc:date>2026-05-21T03:11:08Z</dc:date>
    </item>
    <item>
      <title>Re: Logging to SPLUNK from a JMP script</title>
      <link>https://community.jmp.com/t5/Discussions/Logging-to-SPLUNK-from-a-JMP-script/m-p/950861#M109873</link>
      <description>&lt;P&gt;At least in our SPLUNK instance the separator between Name and VALUE is a colon.&amp;nbsp; So,&amp;nbsp;&lt;BR /&gt;"event" =&amp;gt; "Test message"&lt;/P&gt;
&lt;P&gt;becomes&lt;/P&gt;
&lt;P&gt;"event" : "Test message"&lt;/P&gt;</description>
      <pubDate>Wed, 27 May 2026 16:00:33 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Logging-to-SPLUNK-from-a-JMP-script/m-p/950861#M109873</guid>
      <dc:creator>RC_Flyer</dc:creator>
      <dc:date>2026-05-27T16:00:33Z</dc:date>
    </item>
    <item>
      <title>Re: Logging to SPLUNK from a JMP script</title>
      <link>https://community.jmp.com/t5/Discussions/Logging-to-SPLUNK-from-a-JMP-script/m-p/951016#M109877</link>
      <description>&lt;P&gt;There are several Python packages that support logging to splunk. &amp;nbsp;It's far easier to utilize an existing Python package than having to roll your own REST handling interface code in JSL.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My google query:&amp;nbsp;python package for logging to splunk.&lt;/P&gt;
&lt;P&gt;The top hit was&lt;/P&gt;
&lt;P&gt;&lt;STRONG class="Yjhzub" data-copy-service-computed-style="font-family: &amp;quot;Google Sans&amp;quot;, &amp;quot;Helvetica Neue&amp;quot;, sans-serif; font-size: 16px; font-weight: 600; margin: 0px; text-decoration: none; border-bottom: 0px rgb(10, 10, 10);" data-complete="true" data-sfc-cb="" data-sfc-root="c"&gt;&lt;SPAN class="" data-copy-service-computed-style="font-family: &amp;quot;Google Sans&amp;quot;, &amp;quot;Helvetica Neue&amp;quot;, sans-serif; font-size: 16px; font-weight: 600; margin: 0px; text-decoration: none; border-bottom: 0px rgb(10, 10, 10);" data-complete="true" data-sfc-cb="" data-sfc-root="c" data-sfc-cp=""&gt;&lt;A class="H23r4e" href="https://pypi.org/project/splunk-handler/" rel="noopener" data-copy-service-computed-style="font-family: &amp;quot;Google Sans&amp;quot;, &amp;quot;Helvetica Neue&amp;quot;, sans-serif; font-size: 16px; font-weight: 500; margin: 0px; text-decoration: underline 1px rgb(26, 13, 171); border-bottom: 0px rgb(26, 13, 171);" aria-label="splunk-handler. Link preview. Site: PyPI. Title: splunk-handler - PyPI. URL: https://pypi.org/project/splunk-handler/." data-sb="/url?sa=i&amp;amp;source=web&amp;amp;rct=j&amp;amp;url=https://pypi.org/project/splunk-handler/&amp;amp;ved=2ahUKEwjmyLv1htyUAxVPMlkFHZ2nHkIQy_kOegoIAAgACAEIEBAC&amp;amp;opi=89978449&amp;amp;cd&amp;amp;psig=AOvVaw1nx29mqa1IlNAPKen271wx&amp;amp;ust=1780060143371000" data-hveid="CAAIAAgBCBAQAg" target="_blank"&gt;splunk-handler&lt;/A&gt;&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt;: A popular and widely used asynchronous logging handler that sends events to the Splunk HEC. It is designed to be a "drop-in" replacement for standard Python logging handlers.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;With the Python Integration, you can utilize such packages and call from JSL with the Python Submit() or the Python Execute()&lt;/P&gt;</description>
      <pubDate>Thu, 28 May 2026 13:15:48 GMT</pubDate>
      <guid>https://community.jmp.com/t5/Discussions/Logging-to-SPLUNK-from-a-JMP-script/m-p/951016#M109877</guid>
      <dc:creator>Paul_Nelson</dc:creator>
      <dc:date>2026-05-28T13:15:48Z</dc:date>
    </item>
  </channel>
</rss>

