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
    • New Product Readiness
    • On-Demand Subscriptions
    • Student Resources
    • Upcoming Events
  • 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
Announcement Banner

Users are unable to open Netwitness Support Cases via email. Please open support cases via portal or by phone

View Details
  • NetWitness Community
  • Discussions
  • How to include additional attributes like custom1 and custom2 in event source monitoring template.
  • 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

How to include additional attributes like custom1 and custom2 in event source monitoring template.

KarthikeyanSank
KarthikeyanSank Beginner
Beginner
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

‎2016-06-15 08:39 AM


Hi,

Can some help me on how to include additional attributes like custom1 and custom2 in event source monitoring template. Thanks

  • Community Thread
  • Discussion
  • ESM
  • Event Source Monitoring
  • Forum Thread
  • NetWitness
  • NW
  • NWP
  • RSA NetWitness
  • RSA NetWitness Platform
0 Likes
Share
Reply
  • All forum topics
  • Previous Topic
  • Next Topic
1 REPLY 1

ShawnOstapuk
ShawnOstapuk Beginner
Beginner
Options
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

‎2016-07-29 11:26 AM

If I'm understanding your question correctly, you can't.

 

If you're goal (as an example) is to say monitor for device.type AND msg.id to look for specific events not coming it doesn't work that way. Someone can correct me if I'm wrong, but essentially the ESM is pulling only a specific few targeted meta (collector, device.ip, device.type) stats from all your LDs and using it for notification if something stops logging (I'm guessing it's using the LD's built in stats collection functionality as it already collects stats on that meta).

 

You could try, but it might not work and might cause other problems, creating a additional device.type meta value based on an app rule that includes all the meta you're looking for but those events would now have two pieces of device.type meta and I'm not sure how that would affect the stats collection, your ESA rules, warehouse reporting, etc

 

If you have ESA you can setup an alert and do some window batching to look for zero events. I wish you could setup a report alert to run on a specific schedule. For example if you could have a report alert run every 1 or 4 hours and have rule that only has data by using max_threshold to filter out values > 0 or whatever you consider to be the low count.

0 Likes
Share
Reply
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.