This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject

NetWitness Community

  • Home
  • Products
    • NetWitness Platform
      • Advisories
      • Documentation
        • Platform Documentation
        • Known Issues
        • Security Fixes
        • Hardware Documentation
        • Threat Content
        • Unified Data Model
        • Videos
      • Downloads
      • Integrations
      • Knowledge Base
    • NetWitness Cloud SIEM
      • Advisories
      • Documentation
      • Knowledge Base
    • NetWitness Detect AI
      • Advisories
      • Documentation
      • Knowledge Base
    • NetWitness Investigator
    • NetWitness Orchestrator
      • Advisories
      • Documentation
      • Knowledge Base
      • Legacy NetWitness Orchestrator
        • Advisories
        • Documentation
  • Community
    • Blog
    • Discussions
    • Events
    • Idea Exchange
  • Support
    • Case Portal
      • Create New Case
      • View My Cases
      • View My Team's Cases
    • Community Support
      • Getting Started
      • News & Announcements
      • Community Support Forum
      • Community Support Articles
    • Product Life Cycle
    • Support Information
    • General Security Advisories
  • Training
    • Blog
    • Certification Program
    • Course Catalog
      • Netwitness XDR
      • EC-Council Training
    • New Product Readiness
    • On-Demand Subscriptions
    • Student Resources
    • Upcoming Events
    • Role-Based Training
  • Technology Partners
  • Trust Center
Sign InRegister Now
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
NetWitness Discussions
  • NetWitness Community
  • Discussions
  • Device Down
  • Options
    • Subscribe to RSS Feed
    • Mark Topic as New
    • Mark Topic as Read
    • Float this Topic for Current User
    • Bookmark
    • Subscribe
    • Mute
    • Printer Friendly Page

Device Down

Go to solution
NaushadKasu
NaushadKasu Beginner
Beginner
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2013-06-08 01:41 AM

Has anyone been successful in finding a way to mimic the Device Down functionality from enVision in SA?  I'm looking for something as simple a way to query when a particular device (IP or hostname) last sent logs.  Maybe some alerting can be handled once this timestamp is found to trespass some threshold.

  • Community Thread
  • devicedown
  • Discussion
  • down
  • Forum Thread
  • log
  • Logging
  • NetWitness
  • not
  • NW
  • NWP
  • Outage
  • RSA NetWitness
  • RSA NetWitness Platform
1 Like
Reply
  • All forum topics
  • Previous Topic
  • Next Topic
1 ACCEPTED SOLUTION

Accepted Solutions

Go to solution
RSAAdmin
RSAAdmin Beginner
Beginner
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2013-07-30 05:21 PM

Log Decoder will have a feature in 10.2 SP2 that you can use to track this.  The command /decoder logStats will return all devices and the number of logs received and the UTC timestamp of the last log received.

 

In 10.3, SA will have additional functionality that can be leveraged to alert on these metrics.

View solution in original post

2 Likes
Reply
11 REPLIES 11

Go to solution
RSAAdmin
RSAAdmin Beginner
Beginner
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2013-07-30 05:21 PM

Log Decoder will have a feature in 10.2 SP2 that you can use to track this.  The command /decoder logStats will return all devices and the number of logs received and the UTC timestamp of the last log received.

 

In 10.3, SA will have additional functionality that can be leveraged to alert on these metrics.

2 Likes
Reply

Go to solution
NaushadKasu
NaushadKasu Beginner
Beginner
In response to RSAAdmin
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2013-07-30 05:49 PM

Scott,

 

Appreciate the reply... by log decoder, do you mean all devices including the ones the log collector service running on the decoder is collecting for as well?  I'm hoping that the device down feature will be available in full-feature for example, showing not only syslog collection outage per device (decoder) but also ODBC, File Reader etc... that is collected via Log Collector service.

 

Also when is 10.2 SP2 scheduled for?  We can at least write REST queries to track issues with our log collection until SP3 comes out with the added alerting feature.

0 Likes
Reply

Go to solution
RSAAdmin
RSAAdmin Beginner
Beginner
In response to NaushadKasu
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2013-07-30 05:54 PM

The logStats capability only exists on the log decoder, not the log collector, but on the log decoder it will include all log sources, syslog and those that LC sends to LD.

 

Service Pack 2 is scheduled for later this quarter.

 

BTW, logStats already exists in 10.2 SP1, but will be enhanced for SP2 to include logs received from LC.  SP1 only reports syslog devices.

0 Likes
Reply

Go to solution
NaushadKasu
NaushadKasu Beginner
Beginner
In response to RSAAdmin
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2013-07-30 05:59 PM

Scott,

 

How do you get to that?  Where do I run that command?  Are you talking about on the REST interface?

0 Likes
Reply

Go to solution
RSAAdmin
RSAAdmin Beginner
Beginner
In response to NaushadKasu
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2013-07-30 06:05 PM

Sure, you can run it on the REST interface or in NwConsole or from explorer view.  You just have to send the logStats command to the /decoder node of a Log Decoder.

 

For SP1, you will need to enable the command to track these stats, in SP2 it will be enabled by default.

 

Example:

 

http://<ip>:50102/decoder?msg=logStats&enable=true

 

Then you can just query the stats:

 

http://<ip>:50102/decoder?msg=logStats

 

For SP2, there will be additional functionality where you can query for only certain devices that match a regex and who haven't sent a log outside of a time window you define and pass as a parameter.

2 Likes
Reply

Go to solution
NaushadKasu
NaushadKasu Beginner
Beginner
In response to RSAAdmin
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2013-07-30 06:12 PM

Works!  Looks good man.. thanks!

0 Likes
Reply

Go to solution
SethGeftic
SethGeftic Beginner
Beginner
In response to NaushadKasu
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2013-07-30 08:17 PM

The community in action! I love it

0 Likes
Reply

Go to solution
NaushadKasu
NaushadKasu Beginner
Beginner
In response to RSAAdmin
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2013-07-31 09:12 AM

Scott,

 

Looks like a great feature coming up in SP2... thus far you've mentioned this feature as it relates to Log Decoder (Syslog), are there any plans to incorporate it into the Log Collector service as well so we can track devices like Windows, ODBC, FR etc.. that may also have not sent logs in a particular time frame?

0 Likes
Reply

Go to solution
RSAAdmin
RSAAdmin Beginner
Beginner
In response to NaushadKasu
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Report Inappropriate Content

‎2013-07-31 10:24 AM

In SP2, all logs received on a Log Decoder from a Log Collector will be tracked as well.  So Windows, ODBC, FR, etc, will be tracked in Log Decoder after it's received from a Log Collector.

 

Scott

0 Likes
Reply
  • « Previous
    • 1
    • 2
  • Next »
Powered by Khoros
  • Blog
  • Events
  • Discussions
  • Idea Exchange
  • Knowledge Base
  • Case Portal
  • Community Support
  • Product Life Cycle
  • Support Information
  • About the Community
  • Terms & Conditions
  • Privacy Statement
  • Acceptable Use Policy
  • Employee Login
© 2022 RSA Security LLC or its affiliates. All rights reserved.