05-06-2024 10:07 PM
My name is Zake and i want to ask how to setting severity in Cisco Estream, i use Cisco Firepower 3120 and want ingest log to Azure Sentinel. I was successfull to ingest log but there is too much log i got, when i see there is too much information severity level.
What i already do is change in estreamer.conf, when the default level is "INFO"
"logging": {
"@comment": "Levels include FATAL, ERROR, WARNING, INFO, DEBUG, VERBOSE and TRACE",
"level": "INFO",
"format": "%(asctime)s %(name)-12s %(levelname)-8s %(message)s",
"stdOut": true,
"filepath": "estreamer.log"
},
I was changed it to "WARNING" but there is nothing happen, "INFO" severity still got ingest.
"logging": {
"@comment": "Levels include FATAL, ERROR, WARNING, INFO, DEBUG, VERBOSE and TRACE",
"level": "WARNING",
"format": "%(asctime)s %(name)-12s %(levelname)-8s %(message)s",
"stdOut": true,
"filepath": "estreamer.log"
},
I got wrong way or i need to setting in different way ? Could you help me ?
Solved! Go to Solution.
05-06-2024 11:45 PM
Those options are for eStreamer app logging level and not the logs forwarded from the FMC.
You need to edit the records section of the estreamer.conf.
You have more options to exclude specific records. see documentation here on specific records:
for ex to exclude Connection statistics/flow use record 71 as in the example below:
"records": {
"connections": true,
"core": true,
"excl@comment": [
"These records will be excluded regardless of above (overrides 'include')",
"e.g. to exclude flow and IPS events use [ 71, 400 ]"
],
"exclude": [71],
05-06-2024 11:45 PM
Those options are for eStreamer app logging level and not the logs forwarded from the FMC.
You need to edit the records section of the estreamer.conf.
You have more options to exclude specific records. see documentation here on specific records:
for ex to exclude Connection statistics/flow use record 71 as in the example below:
"records": {
"connections": true,
"core": true,
"excl@comment": [
"These records will be excluded regardless of above (overrides 'include')",
"e.g. to exclude flow and IPS events use [ 71, 400 ]"
],
"exclude": [71],
05-06-2024 11:57 PM
I got confused whatever informational code except 71, already read the documentation you give me link but still confused.
Would you please give me all informational code ? i want to amke it only WARNING to CRIT severity
05-07-2024 01:12 AM
You are not able to filter based on the severity logs on the estreamer config. (like info,critical etc).
You should do this on the Azure side when you configure the Agent and Data Collection Rule.
05-07-2024 01:35 AM
Already setting minimum severity in DCR in Azure Sentinel, but log firewall still ingest informational. I mean if 71 is not too critical i can exclude that, but i need to exclude what code more except 71 ?
05-07-2024 03:04 AM
in DCR in Azure Sentinel, you also need to match both the Facility and log level. I think the facility is LOG_USER
you can use Sentinel to summarize all the events that have informational level and identify all Info logs:
use the below example:
| summarize Count=count() by name
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide