- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
perlish
Communicator
11-05-2012
10:51 PM
1 Solution
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yannK

Splunk Employee
11-05-2012
11:51 PM
Upgrading go not cause a loss of data, the only consequence is when you have to restart Splunk you may miss events send as UDP/TCP.
To accept data all the time, use those techniques :
- splunk forwarders (they can queue and pause monitoring, and use persistent queues)
- rsyslog/syslog-ng to write to file your syslog data (and act as buffer)
- multiple indexers in a load balanced cluster (so you can shut the down one at a time)
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yannK

Splunk Employee
11-05-2012
11:51 PM
Upgrading go not cause a loss of data, the only consequence is when you have to restart Splunk you may miss events send as UDP/TCP.
To accept data all the time, use those techniques :
- splunk forwarders (they can queue and pause monitoring, and use persistent queues)
- rsyslog/syslog-ng to write to file your syslog data (and act as buffer)
- multiple indexers in a load balanced cluster (so you can shut the down one at a time)
