{"id":353751,"date":"2024-09-17T10:59:20","date_gmt":"2024-09-17T10:59:20","guid":{"rendered":"https:\/\/www.ninjaone.com\/script-hub\/monitorare-i-file-di-testo-con-powershell\/"},"modified":"2024-10-13T19:04:30","modified_gmt":"2024-10-13T19:04:30","slug":"monitorare-i-file-di-testo-con-powershell","status":"publish","type":"script_hub","link":"https:\/\/www.ninjaone.com\/it\/script-hub\/monitorare-i-file-di-testo-con-powershell\/","title":{"rendered":"Come utilizzare PowerShell per monitorare i file di testo e attivare gli avvisi per i professionisti IT"},"content":{"rendered":"

Nell’attuale panorama IT, l’automazione \u00e8 fondamentale per gestire e monitorare in modo efficiente i sistemi. PowerShell, con le sue potenti funzionalit\u00e0 di scripting, \u00e8 uno strumento indispensabile per i professionisti IT e i fornitori di servizi gestiti (MSP)<\/a> che desiderano ottimizzare i propri flussi di lavoro. Un’attivit\u00e0 comune \u00e8 il monitoraggio dei file di testo alla ricerca di contenuti specifici, sia che si tratti di tenere traccia dei log, di rilevare errori o di avvisare su informazioni critiche.<\/p>\n

Lo script PowerShell<\/a> che analizziamo oggi serve proprio a monitorare i file di testo e ad avvisare quando un testo specificato viene trovato in un file, funzione che lo rende uno strumento prezioso per chi \u00e8 responsabile dell\u2019integrit\u00e0 e della sicurezza dei sistemi IT.<\/p>\n

Background<\/h2>\n

I file di testo sono spesso utilizzati negli ambienti IT per registrare le attivit\u00e0, memorizzare i dati di configurazione o conservare informazioni critiche. Il monitoraggio di questi file attraverso la ricerca di parole chiave o frasi specifiche \u00e8 fondamentale per vari motivi, come per esempio per rilevare le violazioni della sicurezza<\/a>, garantire la conformit\u00e0 o identificare i guasti del sistema.<\/p>\n

Tradizionalmente, i professionisti IT ispezionano manualmente questi file o utilizzano soluzioni software complesse per monitorarli. Tuttavia, con PowerShell \u00e8 possibile automatizzare questo processo con uno script semplice ma efficace. Questo script \u00e8 particolarmente utile per gli MSP che gestiscono pi\u00f9 clienti e hanno bisogno di un modo affidabile per monitorare i file di testo in ambienti diversi.<\/p>\n

Lo script per monitorare i file di testo:<\/h2>\n
#Requires -Version 4\r\n\r\n<#\r\n.SYNOPSIS\r\n    Alert when the specified text is found in a text file.\r\n.DESCRIPTION\r\n    Alert when the specified text is found in a text file.\r\n.EXAMPLE\r\n    (No Parameters)\r\n    ## EXAMPLE OUTPUT WITHOUT PARAMS ##\r\n\r\nPARAMETER: -Path \"C:\\ReplaceMe\\WithPath\\To\\Text.txt\"\r\n    File path to the text file you would like to monitor.\r\n\r\nPARAMETER: -TextToMatch \"ReplaceMeWithTextToFind\"\r\n   Text to alert on when found.\r\n\r\n.EXAMPLE\r\n    -Path \"C:\\Test-FileMonitor.txt\" -TextToMatch \"bat\"\r\n    \r\n    [Alert] Found Text!\r\n\r\n.EXAMPLE\r\n    -Path \"C:\\Test-FileMonitor.txt\" -TextToMatch \"man\" -MatchOnlyOnWholeWord\r\n    \r\n    Text Not Found!\r\n\r\nPARAMETER: -MatchOnlyOnWholeWord\r\n    Alert only when your given 'Text To Match' is not contained in another word.\r\n\r\nPARAMETER: -CaseSensitive\r\n    Alert only when the casing of your specified 'Text To Match' is identical; for example, alert on 'BAT' but not 'bat'.\r\n.OUTPUTS\r\n    None\r\n.NOTES\r\n    Minimum OS Architecture Supported: Windows 10, Windows Server 2012\r\n    Release Notes: Initial Release\r\nBy 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\r\n[CmdletBinding()]\r\nparam (\r\n    [Parameter()]\r\n    [String]$Path,\r\n    [Parameter()]\r\n    [String]$TextToMatch,\r\n    [Parameter()]\r\n    [Switch]$WholeWordOnly = [System.Convert]::ToBoolean($env:matchOnlyOnWholeWord),\r\n    [Parameter()]\r\n    [Switch]$CaseSensitive = [System.Convert]::ToBoolean($env:caseSensitive)\r\n)\r\n\r\nbegin {\r\n    # Set Dynamic Script Variables\r\n    if($env:textToMatch -and $env:textToMatch -notlike \"null\"){\r\n        $TextToMatch = $env:textToMatch\r\n    }\r\n    if($env:textFilePath -and $env:textFilePath -notlike \"null\"){\r\n        $Path = $env:textFilePath\r\n    }\r\n\r\n    # Check for local administrator rights.\r\n    function Test-IsElevated {\r\n        $id = [System.Security.Principal.WindowsIdentity]::GetCurrent()\r\n        $p = New-Object System.Security.Principal.WindowsPrincipal($id)\r\n        $p.IsInRole([System.Security.Principal.WindowsBuiltInRole]::Administrator)\r\n    }\r\n\r\n    # Check that a path was given and if not error out.\r\n    if (-not $Path) {\r\n        Write-Host \"[Error] A filepath is required!\"\r\n        exit 1\r\n    }\r\n\r\n    # If not given text to match error out.\r\n    if (-not $TextToMatch){\r\n        Write-Host \"[Error] Text to match is required!\"\r\n        exit 1\r\n    }\r\n\r\n    # Error out if script is running without local administrator rights.\r\n    if (-not (Test-IsElevated)) {\r\n        Write-Host \"[Error] Access Denied. Please run with Administrator privileges.\"\r\n        exit 1\r\n    }\r\n\r\n    # Check that the path given exists.\r\n    if (-not (Test-Path -Path $Path)) {\r\n        Write-Host \"[Error] File does not exist!\"\r\n        exit 1\r\n    }\r\n\r\n    # Check that we're given a file and not a folder.\r\n    $File = Get-Item -Path $Path\r\n    if ($File.PSIsContainer) {\r\n        Write-Host \"[Error] Please provide a file path, not a directory.\"\r\n        exit 1\r\n    }\r\n\r\n    $ExitCode = 0\r\n}\r\nprocess {\r\n    # Check if we were given a binary file and if so error out.\r\n    $ByteCount = 1024\r\n    $ByteArray = Get-Content -Path $Path -Encoding Byte -TotalCount $ByteCount\r\n    if ($ByteArray -contains 0 ) {\r\n        Write-Host \"[Error] This script does not support searching binary files!\"\r\n        exit 1\r\n    }\r\n\r\n    # Retrieve file contents.\r\n    $File = Get-Content -Path $Path\r\n\r\n    # If file is empty error out.\r\n    if (-not $File) {\r\n        Write-Host \"[Error] reading file, file is either empty or you do not have permission to read it.\"\r\n        exit 1\r\n    }\r\n\r\n    # Scan through each-line checking for our text.\r\n    $File | ForEach-Object {\r\n        # Based on the parameters given match the text.  \r\n        if (-not $CaseSensitive -and -not $WholeWordOnly -and $_ -like \"*$TextToMatch*\") {\r\n            $Match = $True\r\n        }\r\n\r\n        if ($CaseSensitive -and -not $WholeWordOnly -and $_ -clike \"*$TextToMatch*\") {\r\n            $Match = $True\r\n        }\r\n\r\n        if ($WholeWordOnly -and -not $CaseSensitive -and $_ -match \"\\b$TextToMatch\\b\") {\r\n            $Match = $True\r\n        }\r\n\r\n        if ($WholeWordOnly -and $CaseSensitive -and $_ -cmatch \"\\b$TextToMatch\\b\") {\r\n            $Match = $True\r\n        }\r\n    }\r\n\r\n    # If our text matched alert.\r\n    if ($Match) {\r\n        Write-Host \"[Alert] Found Text!\"\r\n    }\r\n    else {\r\n        Write-Host \"Text Not Found!\"\r\n    }\r\n\r\n    exit $ExitCode\r\n}\r\nend {\r\n    \r\n    \r\n    \r\n}<\/pre>\n
 <\/p>\n\n
Analisi dettagliata<\/h2>\n
Lo script fornito \u00e8 progettato per monitorare i file di testo alla ricerca di contenuti specifici e avvisare l’utente quando il testo viene trovato. Ecco una descrizione passo per passo di come funziona lo script:<\/p>\n
1.\u00a0Impostazione dei parametri<\/strong>:<\/h3>\n