Mike_Moniz
ProfessorJoined 9 years ago
User Profile
Professor
User Widgets
Contributions
Re: New to LM: How do I refer to the local filesystem in an embedded PowerShell script of a DataSource?
You need to provide the value for every instance in a batchscript to not get NoData, so you likely need to output: vb-br1.employee.directory.jccc.AssignedCollectorStats=0 vb-ent1.employee.directory.jccc.AssignedCollectorStats=0 vb-proxy1.employee.directory.jccc.AssignedCollectorStats=0 ...etc Also I'm not sure if you will run into any complications with using "." in instance wildvalue, it looks like it's not illegal and might work, but could be confusing in separating the instance part from the datapoint part. Poll Now and Raw Data pull from the same source (each will separately run your script). The only real difference is that Poll Now runs the check immediately while data from Raw Data is on a schedule/queue. Also Poll Now tests will not add entries to the Raw Data tab. But you also need to keep in mind what instance you are looking at the Raw Data/Poll Now tab for. Since which instance you are looking at in the resource tab will set the wildvalue that LM will filter the output to look for. If those screenshots are really looking at an instance called "AssignedCollectorStats" and showing NoData on the "AssignedCollectorStats" datapoint but Poll Now (from that exact same tab) shows AssignedCollectorStats=0, then I'm not sure. Unless it's some timing/race-condition thing, might want to have LM Support look at it. It is also confusing having them both called "AssignedCollectorStats", might want to try using a different instance name/wildvalue incase your running into some weird bug. Also if you just want to make sure the correct collector is assigned to this device, I would likely suggest making a completely different Datasource without multi-instance, just to check for that situation. Might be simpler.1View0likes1CommentRe: New to LM: How do I refer to the local filesystem in an embedded PowerShell script of a DataSource?
You may want to look at the difference between a DataSource and an EventSource. Kinda the idea for a DataSource is that you throw performance data at LM which can log it and graph it. Along with also doing that, LM can have thresholds that will let you set off alerts. While you can just just have a datapoint of "alert" yes/no, it's not the best way normally. But also the important part for DataSource alerting is that there will be a condition that causes an alert and a condition that clears it. There is a start and end time. If you have something that is just a point-in-time event, where there is no end time, you should look at EventSource, or JobMonitoring or something like that. So we have gone back and forth a lot, but you haven't talked about what you are trying to accomplish in general. Perhaps if we understood that, we can make better suggestions on how to accomplish it.7Views0likes4CommentsRe: New to LM: How do I refer to the local filesystem in an embedded PowerShell script of a DataSource?
If I understand you right. A NoData will not clear an alert. So if your threshold is >=5 and the data is (over time) 1, 1, 1, 6, NoData, NoData, 2, 2, 1, 1... the "6" will cause an alert but it will not clear that alert until it gets a valid value under the threshold. So NoData is not a condition that will clear the alert until it gets the "2" which can then clear it (assuming instant alert/clear).8Views1like6CommentsRe: New to LM: How do I refer to the local filesystem in an embedded PowerShell script of a DataSource?
I never really used that option so never really thought of it as a possible 100% manual process. It might not even been an option when I started using LM (unsure), which may be why it didn't really come up. You may want to reach out to LM support or your rep to see if they can provide more technical details on exactly when it runs.4Views0likes0CommentsRe: New to LM: How do I refer to the local filesystem in an embedded PowerShell script of a DataSource?
The documentation seems to only say "it can be configured to execute only when the DataSource is initially applied to a device, or when the Datasource (or the device it applies to) is updated in some way." I would take that as more than just manually kicking off AD, and likely covers things like updating the device's ip, name, categories, and such. But that is a guess as I never tested that myself. I would assume it might just run as some random time and not rely on it not running.12Views0likes3CommentsRe: New to LM: How do I refer to the local filesystem in an embedded PowerShell script of a DataSource?
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.9Views1like8CommentsRe: New to LM: How do I refer to the local filesystem in an embedded PowerShell script of a DataSource?
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.0Views0likes10Comments
Groups
Inner Circle
Welcome to the Customer Showcase, sponsored by “The Inner Circle “. Feel free to peruse this Customer Story Showcase to read more about what our customers are doing out in the world and how LogicMonitor is supporting their journeys.
11 Posts Open Beta
Open Beta Process During this open beta period, we are asking that your team members flip the toggle and explore all the new features and functionality while attempting to complete their workflows in the new UI. Any identified bugs or feedback on critical functionality loss will help us to ensure your success and value in this new offering. *Please note, depending on what’s discovered, users can always toggle back to the current UI and continue with their work. Identified bugs or Feedback can be submitted through the following routes: Bugs: Please submit directly through the “Submit a Support Ticket” option using your instance. The more specific you can be on where you experienced the bug, the better. Functionality Feedback: Please submit through the “Feedback” option in your LogicMonitor instance and include “New UI” in the Subject line to ensure it’s routed appropriately.
72 Posts
