<?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: Visibility and Monitoring for HEC base Data Ingestion Interruptions in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Visibility-and-Monitoring-for-HEC-base-Data-Ingestion/m-p/758018#M120210</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/253642"&gt;@Nraj87&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;I'm not AI.&lt;/P&gt;&lt;P&gt;Did you read the referenced documentation and experiment with health checks and thresholds?&lt;/P&gt;&lt;P&gt;In general:&lt;/P&gt;&lt;P&gt;1. Model your system's behavior in a controlled environment. What are its principal components (metrics)? What are the shapes/distributions of the metrics?&lt;/P&gt;&lt;P&gt;2. Measure your system's activity. What are the current values of the metrics?&lt;/P&gt;&lt;P&gt;3. Monitor (compare) your measurements to your model. Is the current metric value outside the range of acceptable values based on your model?&lt;/P&gt;</description>
    <pubDate>Thu, 05 Feb 2026 12:57:28 GMT</pubDate>
    <dc:creator>tscroggins</dc:creator>
    <dc:date>2026-02-05T12:57:28Z</dc:date>
    <item>
      <title>Visibility and Monitoring for HEC base Data Ingestion Interruptions</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Visibility-and-Monitoring-for-HEC-base-Data-Ingestion/m-p/756815#M120035</link>
      <description>&lt;P&gt;please advise whether there is a solution or monitoring use case to identify interruptions in HEC base data ingestion.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P class=""&gt;&lt;SPAN&gt;Specifically:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P class=""&gt;&lt;SPAN&gt;When the data ingestion service (HEC Token) becomes unavailable OR Down&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;SPAN&gt;When the service&amp;nbsp;(HEC Token) is operational, but no data/logs are being received during normal business hours.&lt;/SPAN&gt;&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Sun, 28 Dec 2025 08:16:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Visibility-and-Monitoring-for-HEC-base-Data-Ingestion/m-p/756815#M120035</guid>
      <dc:creator>Nraj87</dc:creator>
      <dc:date>2025-12-28T08:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: Visibility and Monitoring for HEC base Data Ingestion Interruptions</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Visibility-and-Monitoring-for-HEC-base-Data-Ingestion/m-p/756819#M120036</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/253642"&gt;@Nraj87&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;You can probe the services/collector/health endpoint on the HEC port for current service, ack, and token status. See &lt;A href="https://help.splunk.com/en/splunk-enterprise/leverage-rest-apis/rest-api-reference/10.0/input-endpoints/input-endpoint-descriptions" target="_self"&gt;https://help.splunk.com/en/splunk-enterprise/leverage-rest-apis/rest-api-reference/10.0/input-endpoints/input-endpoint-descriptions&lt;/A&gt; or your version's documentation for more information.&lt;/P&gt;&lt;P&gt;HEC metrics are available in index=_introspection with sourcetype=http_event_collector_metrics, e.g.:&lt;/P&gt;&lt;P&gt;index=_introspection sourcetype=http_event_collector_metrics component=HttpEventCollector data.series=http_event_collector&lt;/P&gt;&lt;P&gt;index=_introspection sourcetype=http_event_collector_metrics component=HttpEventCollector data.series=http_event_collector_token&lt;/P&gt;&lt;P&gt;| tstats latest(data.num_of_events) as num_of_events latest(data.num_of_requests) as num_of_requests where index=_introspection sourcetype=http_event_collector_metrics component=HttpEventCollector data.series=http_event_collector&lt;/P&gt;&lt;P&gt;| tstats sum(data.num_of_events) as num_of_events sum(data.num_of_requests) as num_of_requests where index=_introspection sourcetype=http_event_collector_metrics component=HttpEventCollector data.series=http_event_collector_token data.token_name=foo by _time&lt;/P&gt;&lt;P&gt;Introspection metrics are relative to the report window, i.e., data.num_of_events is the number of events received over the last 60 seconds using the default limits.conf [http_input] stanza settings. Token-level introspection events are only generated when activity occurs over the report window. See &lt;A href="https://help.splunk.com/en/splunk-enterprise/get-started/get-data-in/10.0/get-data-with-http-event-collector/troubleshoot-http-event-collector" target="_self"&gt;https://help.splunk.com/en/splunk-enterprise/get-started/get-data-in/10.0/get-data-with-http-event-collector/troubleshoot-http-event-collector&lt;/A&gt; for more information.&lt;/P&gt;</description>
      <pubDate>Sun, 28 Dec 2025 15:55:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Visibility-and-Monitoring-for-HEC-base-Data-Ingestion/m-p/756819#M120036</guid>
      <dc:creator>tscroggins</dc:creator>
      <dc:date>2025-12-28T15:55:37Z</dc:date>
    </item>
    <item>
      <title>Re: Visibility and Monitoring for HEC base Data Ingestion Interruptions</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Visibility-and-Monitoring-for-HEC-base-Data-Ingestion/m-p/758016#M120209</link>
      <description>&lt;P&gt;Above Suggestion didn't work,&amp;nbsp;Monitoring should generate an alert whenever the Splunk HEC data connection is disrupted or stops working to prevent data loss.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Feb 2026 12:33:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Visibility-and-Monitoring-for-HEC-base-Data-Ingestion/m-p/758016#M120209</guid>
      <dc:creator>Nraj87</dc:creator>
      <dc:date>2026-02-05T12:33:03Z</dc:date>
    </item>
    <item>
      <title>Re: Visibility and Monitoring for HEC base Data Ingestion Interruptions</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Visibility-and-Monitoring-for-HEC-base-Data-Ingestion/m-p/758018#M120210</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/253642"&gt;@Nraj87&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;I'm not AI.&lt;/P&gt;&lt;P&gt;Did you read the referenced documentation and experiment with health checks and thresholds?&lt;/P&gt;&lt;P&gt;In general:&lt;/P&gt;&lt;P&gt;1. Model your system's behavior in a controlled environment. What are its principal components (metrics)? What are the shapes/distributions of the metrics?&lt;/P&gt;&lt;P&gt;2. Measure your system's activity. What are the current values of the metrics?&lt;/P&gt;&lt;P&gt;3. Monitor (compare) your measurements to your model. Is the current metric value outside the range of acceptable values based on your model?&lt;/P&gt;</description>
      <pubDate>Thu, 05 Feb 2026 12:57:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Visibility-and-Monitoring-for-HEC-base-Data-Ingestion/m-p/758018#M120210</guid>
      <dc:creator>tscroggins</dc:creator>
      <dc:date>2026-02-05T12:57:28Z</dc:date>
    </item>
  </channel>
</rss>

