Fixed Issues
Fixed issues in Splunk App for Stream 6.2.2:
Defect number | Description |
---|---|
STREAM-1926 | The Total Events graph in the Stream Forwarder Metrics dashboard does not populate. |
STREAM-1913 | Splunkd does not reliably shut down streamfwd process. |
STREAM-1909 | SNMP events not returning key pieces of data due to lack of parsing from original binary format. |
STREAM-1871 | HierarchicalProtocolHandler should have a max limit of objects being extracted. |
STREAM-1868 | The streamfwd process dies, produces Out of Memory error. |
STREAM-1866 | Disabling stream(s) doesn't turn off DPI processing for certain protocols. |
STREAM-1864 | Incorrect multicast DNS request/response led to unbounded event size build-up. |
STREAM-1851 | Version number under "About" section of stream app doesn't match with the uploaded image. |
STREAM-1846 | Dashboard searches fail for time periods greater than 60 minutes. |
STREAM-1845 | Add DPI event size limits to prevent the accumulation of many stalled state events that consumed memory. |
STREAM-1836 | Ephemeral Stream did not work as expected. ES 3.2.1 passed createDate attribute as a decimal string, while Stream 6.2 expected integer.
|
STREAM-1797 | Stream Forwarder doesn't generate flow events if one of the endpoints in the flow is a known "missing keys" SSL server. |
STREAM-1795 | Optimized cache management reduces spikes in events generation, which minimizes event queue overflows in high-load environments. |
STREAM-1794 | On Windows, a false "no license" and "license error" message appears at startup in splunkd.log when the streamfwd binary is running as a modular input.
|
STREAM-1793 | Remove DSSL "missing SSL server" checking logic to prevent improper processing of the subsequent SSL flows from undecryptable SSL endpoint. This ensures that Stream processes all flows regardless of whether or not they can be decrypted. |
STREAM-1786 | When you open the CE window for editing, the "Match" selection option resets to "First". |
STREAM-1784 | Limit the number of TCP sessions pruned in a single cleanup run to alleviate the negative effects an unbound cleanup process creates. |
STREAM-1783 | TCP session cleanup occurs simultaneously for all processing threads which causes an event spike that may lead to event queue overflow. Stagger the processing of thread cleanup timing to spread the TCP session cleanup overhead. |
STREAM-1745 | In list of pop3 protocol attributes "login_server" is misspelled as "login_servier." |
Known issues | Credits |
This documentation applies to the following versions of Splunk Stream™: 6.2.2
Feedback submitted, thanks!