Forum Discussion

SteveDahlberg's avatar
SteveDahlberg
Icon for Neophyte rankNeophyte
27 days ago

New to LM: How do I refer to the local filesystem in an embedded PowerShell script of a DataSource?

How do I refer to the local filesystem in an embedded PowerShell script of a DataSource? The below works fine from a PowerShell session console on a Collector server, but fails when running embedded ...
  • Mike_Moniz's avatar
    Mike_Moniz
    25 days ago

    Yes, and you see it worked for me in my screenshot with a full path. The only thing I'm aware of that LM will do to a powershell script is do a search-and-replace of ##TOKEN## but I didn't see any of that in your code. Even your error message isn't show the path getting screwed up and it's powershell telling you the file doesn't exist there.

    I would 100% make sure the script is actually running on the server you think it's running on. Does "Write-Output $env:computername" show the name of the server with the file?

SteveDahlberg's avatar
SteveDahlberg
Icon for Neophyte rankNeophyte

For some reason I'm unable to start a new discussion right now, just says:

Cannot add message
Something went wrong, please try again,

But I've been stumped on the following issue and it's driving me nuts:

How do I read the values of instance-level properties in an embedded PowerShell DataSource Collection script? Or resource-level properties in an embedded PowerShell PropertySource? I understand how to write properties and their values in the Active Discovery script with something like 

Write-Host "<instanceID>##<instanceName>##<instanceDescription>####auto.AssignedCollectorDeviceName=$AssignedCollectorDeviceName"

I have an instance-level custom property "auto.AssignedCollectorDeviceName" on a resource instance that I would like to check the value of during Collection script execution, and create my key-value pair for script output based on that value. But I can't for the life of me figure out how to reference and check the host resource's properties while the script is running.  

Also, my first thought was to have the custom property ("AssignedCollectorDeviceName" in that case) at the resource level, and check it while the Collection scripts runs, but realized I (don't think) I can read a resource-level property in that case, only instance-level properties, but I can't even figure out how to do that (without using the API). So in addition to using the auto property at the instance-level, maybe a PropertySource would be better? I'd like to learn how to make and use one, but in its script I think I would have the same problem of reading the value of resource property in order to do the logic to form the script output.

Mike_Moniz's avatar
Mike_Moniz
Icon for Professor rankProfessor
11 days ago

The forum are having more problems :P

You should be able to read any resource property from either AD or Collection script by doing $Prop = '##auto.AssignedCollectorDeviceName##' just like you can use $Host = '##SYSTEM.HOSTNAME##'. Just note that if the property does not exist, it will not get replaced, so you might want to add code that looks something like this

$CollectorDev = '##auto.AssignedCollectorDeviceName##'
if ($CollectorDev.SubString(0,2) -eq '##') { $CollectorDev = $null }

But for an instance property, I haven't tried to pull that myself. If I needed the same information that the AD script had, I would just put the same code into the Collection script. Since 90% of the DataSources scripts I've done has been BatchScripts, many times the AD and Collector scripts are identical except that it has an "IsAD" true/false flag that branches what it outputs at the end.

 

In general, you should only put in items related to the specific instance into the instance property. If you have information that is specific to the device itself, I do suggest you use a PropertySource instead.

For example, for a disk space check, you might want to have auto.filesystem=ntfs or auto.removable=true at the instance-level since they can change per instance. But if you want to set something like auto.TotalSataPorts=4 would be better to put in a ProperySource since it's about the device and not each drive.

  • SteveDahlberg's avatar
    SteveDahlberg
    Icon for Neophyte rankNeophyte
    9 days ago

    Thanks, Mike. And yes, that stumped me for the longest time, but a few weeks ago when looking through other DataSource scripts in LM, I saw that they just used a flag at top, and that's what I've been doing for a while now.

    Most of this I had questions about is working, but right when it seems so close, I'm trying to force a new datapoint to alert based on a key-value pair with value=1 (like I use in some other datapoints in this DataSource that work fine), but it isn't working.

    On the raw data page for the instance in question, "Poll Now", it clearly shows it's sending a 1 to this new datapoint and NaN to the rest, but when I close that and look at the Raw Data table, it shows "NoData" in the column for that datapoint. Any idea what could cause that? It's configured identically to similar datapoints in the DataSource, but what could be changing the value from 1 to NoData between "Poll Now" and the Raw Data table?

    - Steve

     

    • Mike_Moniz's avatar
      Mike_Moniz
      Icon for Professor rankProfessor
      9 days ago

      If you can provide a screenshot of the full Poll Now screen and the No Data table showing the issue.

      Also double check that Range for that datapoint. Blank min/max means no mix/max (so ok to leave blank) but make sure it's not considering the value out of range.

      • SteveDahlberg's avatar
        SteveDahlberg
        Icon for Neophyte rankNeophyte
        9 days ago

        I resolved it a bit ago by forcing the script in Collection mode to send a 1 to the datapoint. But yes, there was a strange disconnect. Anyway, there is what I noted this morning after doing that, and I was literally about to post this question:

        What could cause an alert to hang on once the underlying cause in the instance has quit notifying the datapoint from the Collection script? Alert history shows it alerted once last night then stopped, which is correct (was a test). Collection is not sending it any data, none shown received in Raw Data or Poll Now, and I confirmed with debug outputs that the block that can send 1 to the datapoint is not being executed, but still it won't clear. However, it cleared immediately when I forced-sent 0 to it.