Getting Data In

Logs sending being cutoff

STU3
Engager

Hello,

I have had an issue where specifically the firewall logs were cutoff for about 5 hours and then reconnected and started logging again in Splunk.

The syslog server responsible is actually running and sending data, but how can I troubleshoot why the logs were not sent during that specific time period ?

I am new to troubleshooting indexers etc. any help is appreciaited.

Regards,

0 Karma

STU3
Engager

PS by "syslog server responsible" I meant the firewall management software responsible was logging all the events at the time of cutoff, might have used a wrong term there

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Self-Healing Pipeline Is Now Generally Available: AI-Powered CIM Compliance

Maintaining data integrity across security and analytics pipelines is an ongoing challenge. Data ...

Meet Splunk Observability Studio: AI-Assisted OpenTelemetry Instrumentation Without ...

Instrumentation is usually the last step or even an afterthought when building out a project. The feature ...

Federated Search for Cisco Security and Analytics Logging (SAL) is now GA on Splunk ...

Federated Search for Cisco  Security Analytics and Logging (SAL) is now generally available as part of the ...