SW Powershell Help with Credential for Monitoring field when prompted by the script

This is the current code we are using to run a SQL command to return a value. I'm trying to pass the Credentials for monitoring for the login. We cant seem to figure out how to use the ${CREDENTIAL} variable Specified from link:

Create a Windows PowerShell monitor

$avg = Get-WmiObject win32_process -Credential '${CREDENTIAL}'

$ServerName = "fnsqlapplog1.fna.local"

$DatabaseName = $args[0]

clear

$Query = "SELECT COUNT (*) as [Returned]

FROM

(SELECT

[TimeStampUTC]

,CASE WHEN ISNULL([ExtendedInternalLog],'') = '' THEN NULL ELSE CAST(JSON_VALUE([ExtendedInternalLog], '$.Properties.StatusCode') AS INT) END AS [StatusCode]

FROM [$DatabaseName].[dbo].[Log]

WHERE TimeStampUTC > DATEADD(mi,-5,GETUTCDATE())

AND UserInfo=SYSTEM_USER

) AS t

WHERE t.StatusCode BETWEEN 400 AND 499"

#Action of connecting to the Database and executing the query and returning results if there were any.

$conn=New-Object System.Data.SqlClient.SQLConnection

$ConnectionString = "Server={0};Database={1};Connect Timeout=30" -f $ServerName,$DatabaseName

$conn.ConnectionString=$ConnectionString

$conn.Open()

$cmd=New-Object system.Data.SqlClient.SqlCommand($Query,$conn)

$cmd.CommandTimeout=120

$ds=New-Object system.Data.DataSet

$da=New-Object system.Data.SqlClient.SqlDataAdapter($cmd)

[void]$da.fill($ds)

$conn.Close();

$rValue = $ds.Tables[0].Rows[0][0];

Write-Host "Statistic.4xxCount: " $rValue;

Find more posts tagged with

powershell script

security credentials

Accepted answers

All comments

mesverrum

I don't know why that wouldn't work but this is the syntax I have typically seen/used

$Creds = Get-Credential ${CREDENTIAL}

sturdyerde

If you configure this PowerShell component monitor in your application template to inherit its credential from the node, the node's credentials should pass through to the ${CREDENTIAL} variable without problem.

m-milligan

Most of my PowerShell monitors do this to get the user name and password from the ${CREDENTIAL} variable:

$c = Get-Credential -credential ${CREDENTIAL};
[string] $user = $c.Username;
[string] $password = $c.GetNetworkCredential().password;

To connect to an Oracle database, build your connection string with $user and $password, then use it establish the database connection:

$conn_string = "User Id=$user;Password=$password;Data Source=(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=$hostname)(PORT=$port))(CONNECT_DATA=(SERVICE_NAME=$serviceName)))";
try {
  $conn = New-Object Oracle.ManagedDataAccess.Client.OracleConnection($conn_string);
} catch {
  Write-Host "Message: Failed to connect to service $serviceName at $hostname`:$port. Error: $($Error[0])";
  exit 1;
}

sturdyerde

With my PowerShell monitors, I sometimes have trouble with Orion variables resolving directly in cmdlet parameters. The workaround has been to save the Orion variable to a PowerShell variable at the top of the script, and then reference the PowerShell variable in code.

Try using this at the top:

$c = Get-Credential ${CREDENTIAL}

and then:

$avg = Get-WmiObject win32_process -Credential $c

jrouviere

I was having the same issue and this helped resolve it, thank you!