Get-CacheLogs - Monitor Cache Performance
This fetches a specified log file from the cache server and places it at the specified destination location on the machine to monitor cache performance. You can also specify multiple log files or all log files to be fetched and placed at the desired location to monitor cache performance.
Note
This feature is available in NCache Enterprise and Professional.
Get-CacheLogs [-Server] [-FileNames] [-Location] [-Port] [-NoLogo] [-Credentials]
Examples of Get-CacheLogs - Monitor Cache Performance
- The example given below copies all log files from server 20.200.20.11 to the destination directory to monitor cache performance.
Get-CacheLogs -FileNames -Destination "C:\Logfile-path" -Server 20.200.20.11
- The following example copies the specified files from server 20.200.20.11 to the destination directory.
Get-CacheLogs -FileNames "demoCache_20-5-2020-14-9-32_192.168.10.13.txt,demoClusteredCache_20-5-2020-14-9-34_192.168.10.13.txt" -Destination "C:\Logfile-path" -Server 20.200.20.11
Properties
Note
The parameters with asterisk (*) on their names are the required parameters and the rest are optional.
Parameters | Data Types | Description | Default Value |
---|---|---|---|
-Server* |
<String> |
Specifies the server address where the log files are residing. | - |
-FileNames* |
<String> |
Specifies the name of the log file (with filename extension) which needs to be copied at the target path provided. NOTE: Comma (,) separated log file names must be specified in case of multiple files. To select all files, use asterisk (*) |
- |
-Location* |
<String> |
Specifies the location where the log file needs to be copied at your machine. | - |
-Port |
<Integer> |
Specifies the server port if the server channel is not using the default port. | 8250 |
-NoLogo |
<SwitchParameter> |
Suppresses display of the logo banner. | False |
-Credentials |
<pscredential> |
Specifies the user credentials required to authorize access for the specified operation. These credentials should belong to a user who has appropriate permissions at the node. | - |