Linux Proficiency

1. Update a file to set the execution permission for the owner’s group.
2. In the attached ZIP file, you will find some sample logs in a file named “sample.log”. Each log
starts with a log level—also called “SeverityText”—that comes after the timestamp. The log
levels are ERROR, INFO, and WARNING. Here is a sample with the log level highlighted in green.
[2021-08-20T00:00:00,321][ERROR][logstash.inputs.azureblobstorage] caught: BlobNotFound
(404): The specified blob does not exist.
Time:2021-08-20T00:00:00.3001445Z for full_read
Parse out that field and output it to a local output file. You may use either NXLog or syslog-ng. You only
need to perform this task in a single log agent.
If you choose NXLog, the attached NXLog.conf will get you started. The log level needs to be output via
the variable in line 51. Right now, that variable has a dummy value output to it, but you can change that
as you please.
If you choose syslog-ng, the log level needs to be output via the JSON statement in line 23. Since that
line is particularly long and a little confusing, I have highlighted the SeverityText output field here:
“PROGRAM {“Timestamp”: “${YEAR}-${MONTH}-
${DAY}T${HOUR}:${MIN}:${SEC}${TZOFFSET}”, “SeverityText”:””, “Resource”:
{“mfc_ver”: “1”, “ci_num”: “CIXXXXX”, “top_level_ci_num”: “CIXXXXX”,
“owning_segment”: “ets”, “app_name”: “APPNAME”, “env”: “dev”, “app_comp”:
“APPCOMP”, “sec_flag”: “false”, “pii_flag”: “false”}, “Attributes”: {}, “Body”:
“$MSG” }n”)
Right now, that field is blank, but you can populate it as you prefer.
Please share with us the configuration file that you updated. Please ensure that the file is ready to run
as long as we change the paths of the input and output files appropriately for our machine.