Скачать или смотреть Extracting Directory Names and Logs from Paths in PowerShell

Learn how to effectively extract directory names from file paths in `PowerShell`, and how to utilize the extracted data for logging operations in your scripts.
---
This video is based on the question https://stackoverflow.com/q/73293848/ asked by the user 'ontljoshi' ( https://stackoverflow.com/u/19638308/ ) and on the answer https://stackoverflow.com/a/73308474/ provided by the user 'ontljoshi' ( https://stackoverflow.com/u/19638308/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: would like to extract words from a path - powershell

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Extracting Directory Names and Logs from Paths in PowerShell

Introduction to the Problem

Are you dealing with multiple directory paths in PowerShell and need to extract specific names for logging purposes? If you have paths like the following:

C:\Program Files\Atlassian\JIRA\logs\

C:\Program Files\Atlassian\Confluence\logs\

C:\Atlassian\ApplicationData\Bitbucket\log

C:\Atlassian\bitbucket-backup-client-4.0.0\backups\

You might want to change the structure of your logging output. Perhaps you want to format them into friendly names followed by log details. This can save you time and help keep everything organized. Fortunately, PowerShell allows us to manipulate strings and paths effectively to achieve this.

Solution Overview

To extract words from your directory paths and display them neatly, we will follow a structured approach:

Import CSV Configuration: Load path configurations from a CSV file.

Start a Logging Session: Use the Start-Transcript cmdlet to begin logging output.

Extract Names: Iterate through the paths to fetch the necessary directory names and display corresponding logs.

Step-by-Step Breakdown

1. Importing Path Configuration from CSV

First, you’ll need to create a CSV file containing your directory paths. For this example, let’s assume you have a file named HousekeepConfig.csv saved at E:\Backup\Scripts\. To import this file, you can use the following command:

[[See Video to Reveal this Text or Code Snippet]]

This command will store the values of the CSV into the $config variable.

2. Starting a Logging Session

Before you start processing the files, initiate a logging session using Start-Transcript. This feature is handy for capturing all output sent to the console:

[[See Video to Reveal this Text or Code Snippet]]

With the above code, all your following commands will be recorded in the specified log file.

3. Extracting Names and Displaying Logs

Now you can iterate through the imported configuration to extract the names from the paths. You can use the foreach loop for this purpose:

[[See Video to Reveal this Text or Code Snippet]]

In this code snippet:

Split-Path -Leaf is used to pull the final part of the path, which gives you the directory name (like "JIRA" or "Confluence").

Write-Host outputs the formatted string, making it easy to read.

4. Concluding the Logging Session

Once you have completed your operations and logged the necessary information, gracefully stop the logging session using:

[[See Video to Reveal this Text or Code Snippet]]

The completed logging process will now be available in your specified log file.

Conclusion

By following these steps, you’ll be able to extract meaningful directory names from your paths and present them in an organized logging format within PowerShell. This process streamlines your logging efforts and makes it easier to reference files related to each application. Try this approach in your next script for better management of your logging data!