{"id":353748,"date":"2024-09-17T06:06:49","date_gmt":"2024-09-17T06:06:49","guid":{"rendered":"https:\/\/www.ninjaone.com\/script-hub\/script-per-cercare-un-testo-nei-file-di-log-su-macos\/"},"modified":"2024-10-18T12:11:42","modified_gmt":"2024-10-18T12:11:42","slug":"script-per-cercare-un-testo-nei-file-di-log-su-macos","status":"publish","type":"script_hub","link":"https:\/\/www.ninjaone.com\/it\/script-hub\/script-per-cercare-un-testo-nei-file-di-log-su-macos\/","title":{"rendered":"Come cercare un testo nei file di log su macOS con uno script Bash personalizzato"},"content":{"rendered":"

Nell’attuale panorama IT, il monitoraggio e la gestione efficiente dei file di log \u00e8 fondamentale per mantenere l\u2019integrit\u00e0 del sistema e garantire la sicurezza. Che tu sia un professionista IT o un Managed Service Provider (MSP)<\/a>, la possibilit\u00e0 di ricercare e segnalare rapidamente un testo specifico all’interno di un file di log pu\u00f2 essere uno strumento potente nel tuo arsenale. In questo articolo presenteremo uno script Bash<\/a> personalizzato progettato per cercare un testo nei file di log su macOS<\/a> e avvisare gli utenti.<\/strong><\/p>\n

L’importanza del monitoraggio dei file di log<\/h2>\n

I file di log sono una componente fondamentale per il funzionamento e la manutenzione dei sistemi IT. Contengono le registrazioni di eventi, processi ed errori che si verificano in un computer o in una rete. Analizzando i file di log, i professionisti IT possono identificare i problemi, rintracciarne la causa principale e garantire la conformit\u00e0 ai requisiti normativi. Tuttavia, controllare manualmente questi file per trovare le informazioni rilevanti pu\u00f2 richiedere molto tempo ed \u00e8 un\u2019attivit\u00e0 che pu\u00f2 essere soggetta a errori umani<\/a>.<\/p>\n

\u00c8 qui che entra in gioco l\u2019automazione<\/a>. L’automazione del processo di monitoraggio dei file di log e l’attivazione di avvisi quando viene rilevato un testo specifico possono far risparmiare tempo e ridurre il rischio di trascurare problemi critici. Lo script di cui parleremo \u00e8 una soluzione semplice ma efficace per ottenere questo risultato su macOS.<\/p>\n

Lo script per cercare un testo nei file di log su macOS:<\/h2>\n
#!\/usr\/bin\/env bash\r\n\r\n# Description: Alert when the specified Text is found in a text file.\r\n#\r\n# Release Notes: Initial Release\r\n#   By using this script, you indicate your acceptance of the following legal terms as well as our Terms of Use at https:\/\/www.ninjaone.com\/terms-of-use.\r\n#   Ownership Rights: NinjaOne owns and will continue to own all right, title, and interest in and to the script (including the copyright). NinjaOne is giving you a limited license to use the script in accordance with these legal terms. \r\n#   Use Limitation: You may only use the script for your legitimate personal or internal business purposes, and you may not share the script with another party. \r\n#   Republication Prohibition: Under no circumstances are you permitted to re-publish the script in any script library or website belonging to or under the control of any other software provider. \r\n#   Warranty Disclaimer: The script is provided \u201cas is\u201d and \u201cas available\u201d, without warranty of any kind. NinjaOne makes no promise or guarantee that the script will be free from defects or that it will meet your specific needs or expectations. \r\n#   Assumption of Risk: Your use of the script is at your own risk. You acknowledge that there are certain inherent risks in using the script, and you understand and assume each of those risks. \r\n#   Waiver and Release: You will not hold NinjaOne responsible for any adverse or unintended consequences resulting from your use of the script, and you waive any legal or equitable rights or remedies you may have against NinjaOne relating to your use of the script. \r\n#   EULA: If you are a NinjaOne customer, your use of the script is subject to the End User License Agreement applicable to you (EULA).\r\n#\r\n# Text to trigger on: [Alert]\r\n#\r\n# Below are all the valid parameters for this script.\r\n# Preset Parameter: --file \"\/opt\/MyLogFile.log\" --text batman\r\n#   Alerts when the text \"batman\" is found in the file \/opt\/MyLogFile.log\r\n#    This is Case Sensitive\r\n#     Example where it will alert: \"I am batman!\"\r\n#     Example where it will alert: \"Iambatman!\"\r\n#     Example where it will not alert: \"IamBatman!\"\r\n#     Example where it will not alert: \"I am Batman!\"\r\n#\r\n# Preset Parameter: --file \"\/opt\/MyLogFile.log\" --text Batman --caseInsensitive true\r\n#   Alerts when the text \"Batman\" is found in the file \/opt\/MyLogFile.log, but is case insensitive\r\n#    This is Case Insensitive\r\n#     Example where it will alert: \"I am batman!\"\r\n#     Example where it will alert: \"Iambatman!\"\r\n#\r\n# Preset Parameter: --file \"\/opt\/MyLogFile.log\" --text Batman --wholeWord true\r\n#   Alerts when the text \"Batman\" is found in the file \/opt\/MyLogFile.log, but only if it is a word in a sentence.\r\n#    This is Case Sensitive\r\n#     Example where it will alert: \"I am Batman!\"\r\n#     Example where it will not alert: \"IamBatman!\"\r\n#\r\n\r\n# Determines whether or not help text is necessary and routes the output to stderr\r\ndie() {\r\n    local _ret=\"${2:-1}\"\r\n    test \"${_PRINT_HELP:-no}\" = yes && print_help >&2\r\n    echo \"$1\" >&2\r\n    exit \"${_ret}\"\r\n}\r\n\r\n# Function that evaluates whether a value passed to it begins by a character\r\n# that is a short option of an argument the script knows about.\r\n# This is required in order to support getopts-like short options grouping.\r\nbegins_with_short_option() {\r\n    local first_option all_short_options='ftiwh'\r\n    first_option=\"${1:0:1}\"\r\n    test \"$all_short_options\" = \"${all_short_options\/$first_option\/}\" && return 1 || return 0\r\n}\r\n\r\n# THE DEFAULTS INITIALIZATION - OPTIONALS\r\n_arg_file=\r\n_arg_text=\r\n_arg_caseInsensitive=\"false\"\r\n_arg_wholeWord=\"false\"\r\n\r\n# Help text function for when invalid input is encountered\r\nprint_help() {\r\n    printf '%s\\n' \"Alert when the specified Text is found in a text file.\"\r\n    printf 'Usage: %s [-f|--file [path to file]] [-t|--text [text to search]] [-i|--caseInsensitive <true|false>] [-w|--wholeWord <true|false>] [-h|--help]\\n' \"$0\"\r\n    printf '\\t%s\\n' \"-f, --file: path to a log file\"\r\n    printf '\\t%s\\n' \"-t, --text: text to alert when found\"\r\n    printf '\\t%s\\n' \"-i, --caseInsensitive: search text with case insensitivity (default: false)\"\r\n    printf '\\t%s\\n' \"-w, --wholeWord: search for text as a whole word (default: false)\"\r\n    printf '\\t%s\\n' \"-h, --help: Prints help\"\r\n}\r\n\r\n# Grabbing the parameters and parsing through them.\r\nparse_commandLine() {\r\n    while test $# -gt 0; do\r\n        _key=\"$1\"\r\n        case \"$_key\" in\r\n        -f | --file)\r\n            test $# -lt 2 && die \"Missing value for the optional argument '$_key'.\" 1\r\n            _arg_file=\"$2\"\r\n            shift\r\n            ;;\r\n        --file=*)\r\n            _arg_file=\"${_key##--file=}\"\r\n            ;;\r\n        -f*)\r\n            _arg_file=\"${_key##-f}\"\r\n            ;;\r\n        -t | --text)\r\n            test $# -lt 2 && die \"Missing value for the optional argument '$_key'.\" 1\r\n            _arg_text=\"$2\"\r\n            shift\r\n            ;;\r\n        --text=*)\r\n            _arg_text=\"${_key##--text=}\"\r\n            ;;\r\n        -t*)\r\n            _arg_text=\"${_key##-t}\"\r\n            ;;\r\n        -i | --caseInsensitive)\r\n            test $# -lt 2 && die \"Missing value for the optional argument '$_key'.\" 1\r\n            _arg_caseInsensitive=\"$2\"\r\n            shift\r\n            ;;\r\n        --caseInsensitive=*)\r\n            _arg_caseInsensitive=\"${_key##--caseInsensitive=}\"\r\n            ;;\r\n        -i*)\r\n            _arg_caseInsensitive=\"${_key##-i}\"\r\n            ;;\r\n        -w | --wholeWord)\r\n            test $# -lt 2 && die \"Missing value for the optional argument '$_key'.\" 1\r\n            _arg_wholeWord=\"$2\"\r\n            shift\r\n            ;;\r\n        --wholeWord=*)\r\n            _arg_wholeWord=\"${_key##--wholeWord=}\"\r\n            ;;\r\n        -w*)\r\n            _arg_wholeWord=\"${_key##-w}\"\r\n            ;;\r\n        -h | --help)\r\n            print_help\r\n            exit 0\r\n            ;;\r\n        -h*)\r\n            print_help\r\n            exit 0\r\n            ;;\r\n        *)\r\n            _PRINT_HELP=yes die \"FATAL ERROR: Got an unexpected argument '$1'\" 1\r\n            ;;\r\n        esac\r\n        shift\r\n    done\r\n}\r\n\r\nparse_commandLine \"$@\"\r\n\r\ntext=$_arg_text\r\nfile=$_arg_file\r\ncaseInsensitive=$_arg_caseInsensitive\r\nwholeWord=$_arg_wholeWord\r\n\r\n# Check if Script Variables where used and overwrite command line parameters\r\nif [[ -n \"${textToMatch}\" ]]; then\r\n    text=$textToMatch\r\nfi\r\nif [[ -n \"${textFile}\" ]]; then\r\n    file=$textFile\r\nfi\r\nif [[ -n \"${matchWholeWord}\" ]]; then\r\n    wholeWord=$matchWholeWord\r\nfi\r\nif [[ -n \"${insensitiveToCase}\" ]]; then\r\n    caseInsensitive=$insensitiveToCase\r\nfi\r\n\r\n# Check if text is not an empty string\r\nif [[ -z \"${text}\" ]]; then\r\n    echo \"[Error] Text not specified\"\r\n    exit 2\r\nfi\r\n\r\n# Check if text is not an empty string\r\nif [[ -z \"${file}\" ]]; then\r\n    echo \"[Error] File not specified\"\r\n    exit 2\r\nfi\r\n\r\n# Does file exit and is readable\r\nif [ -f \"${file}\" ]; then\r\n    echo \"[Info] File \\\"${file}\\\" exists\"\r\n    if [ -r \"${file}\" ]; then\r\n        echo \"[Info] File \\\"${file}\\\" is readable\"\r\n    else\r\n        echo \"[Error] File \\\"${file}\\\" is not readable\"\r\n        exit 2\r\n    fi\r\nelse\r\n    echo \"[Error] File \\\"${file}\\\" does not exists\"\r\n    exit 2\r\nfi\r\n\r\n# Detect\r\ncount=0\r\nif [[ \"${wholeWord}\" == \"true\" ]]; then\r\n    if [[ \"${caseInsensitive}\" == \"true\" ]]; then\r\n        count=$(grep -c -i -n -w \"$text\" \"$file\")\r\n    else\r\n        count=$(grep -c -n -w \"$text\" \"$file\")\r\n    fi\r\nelse\r\n    if [[ \"${caseInsensitive}\" == \"true\" ]]; then\r\n        count=$(grep -c -i -n -e \"$text\" \"$file\")\r\n    else\r\n        count=$(grep -c -n -e \"$text\" \"$file\")\r\n    fi\r\nfi\r\n\r\n# Alert\r\nif ((count > 0)); then\r\n    echo \"[Alert] Found text in file\"\r\n    exit 1\r\nelse\r\n    echo \"[Info] Not found text in file\"\r\n    exit 0\r\nfi\r\n<\/pre>\n
 <\/p>\n\n
Accedi a oltre 700 script nel Dojo di NinjaOne Ottieni l’accesso<\/a><\/p>\n<\/div>\n
Comprendere lo script<\/h2>\n
Lo script fornito \u00e8 uno script Bash progettato per cercare un testo specifico all’interno di un file di log e attivare un avviso se tale testo viene trovato. Consente agli utenti di personalizzare i parametri di ricerca, ad esempio se la ricerca deve essere sensibile alle maiuscole o se deve corrispondere solo a parole intere. Ecco una descrizione dettagliata del funzionamento dello script.<\/p>\n
Inizializzazione dello script<\/h3>\n
Lo script per cercare un testo nei file di log su macOS inizia definendo alcune funzioni per gestire gli errori, verificare la validit\u00e0 degli argomenti e visualizzare le informazioni di aiuto. La funzione die(), per esempio, viene utilizzata per terminare lo script e visualizzare un messaggio di errore se qualcosa va storto. Questa funzione stampa anche il testo di aiuto se viene fornita l’opzione –help.<\/p>\n
Impostazione dei parametri predefiniti<\/h3>\n
Lo script per cercare un testo nei file di log su macOS inizializza diversi parametri predefiniti:<\/p>\n