Stefan_W
NeophyteJoined 6 years ago
User Profile
Neophyte
User Widgets
Contributions
Re: Module Toolbox AppliesTo IDE
For what it's worth... I did just (finally) write up & submit a formal Customer Feedback request and alerted our CSM about it, regarding the lack of calling out the Technical Notes markup as being officially Markdown. Of course until / unless mentions of Markdown make it into the docs and/or UI we probably can't call it "officially Markdown" but that's the info I got back from our CSM when I first asked about it.20Views0likes0CommentsRe: Module Toolbox AppliesTo IDE
For the #2 question about "markup" on Technical Notes... It seems like it is indeed Markdown from some experimentation I did. https://www.markdownguide.org/basic-syntax/ I asked our CSM if we can get a definitive answer on that, and hopefully it added to the docs.33Views1like1CommentRe: Monitoring Top 10 processes on Windows and Linux platforms
FYI I'm working right now on a DataSource which will use SNMP for collecting process memory, CPU, etc. from Linux hosts, instead of calling "ps" via SSH which is what Stuart's does. I am hoping to make a viable version which will indeed create Instances for only the "Top X" based on memory usage, which I'm hoping is consistent enough that if "X" is at least 15 or 20 (number of Instances to be created) then with AD running every 15 minutes there won't be so much turnover on the Instances as to be useless. (I'm starting off with the PID as the Wildvalue.) If that doesn't work I might try making the Wildvalue out of the process name in the hopes that there will be some consistency there instead. In general trying to capture the "Top X" utilization for dynamic things like processes is a balancing act between collecting metrics for everything vs. not enough. I'm hoping that the SNMP Collect (batch script) won't be too hard-hitting on the device or Collector, because it ought to be just 3 SNMP walks total per collect - similar to the LM Core DS "LinuxNewProcesses" locator PMEZLA (except that one is Script not Batchscript)16Views0likes0CommentsRe: A method to identify that a Datasource has been executed via "Poll Now" rather than standard collection, to allow additional info to be displayed conditionally.
As I'm doing more and more custom DataSource development which leverages the Collector ScriptCache I am also finding I am desperately wanting this feature also. In my situation I am working with an API query which specifies a time "window" (start time and end time) to return a set of events which occurred during that time period. The current execution time of the collection run gets saved into ScriptCache to be used as the starting time for the next execution. The problem is that a Poll Now will update the ScriptCache with the time that the Poll Now happened (but the Poll Now data is not collected of course) so at the next data collection the "window" going into the API parameters is too narrow and I'm losing data!!! Basically I need to be able to do something like this: if ( taskProps.get( "how_am_I_being_run" ) == "pollNow" ) { // something which does NOT update Collector ScriptCache } else { // something which does update Collector ScriptCache } (Every time I do a Test Script on the DataSource I also lose data but I can do a clunky work-around during development by working with a clone that has a different ScriptCache item name hard-coded into the Groovy. That's ugly though.) The big issue is that for such a DataSource - where a time "window" is being saved for next-execution - doing a Poll Now causes data loss. Period.14Views3likes0CommentsIdeas for tracking LM website docs changes?
Hi gang! I’ve raised this issue to our CSM but I want to raise the topic here for conversation. There might be a technical solution I’m not imagining. When LogicMonitor updates their own support documents on their website, there’s no way to see what exactly has changed - unless the page content explicitly includes such details. Case in point: “Tokens Available in LogicModule Alert Messages” https://www.logicmonitor.com/support/logicmodules/about-logicmodules/tokens-available-in-datasource-alert-messages It reads “Last updated on 13 January, 2023” OK, great - but what changed?? (We make extensive use of Alert Tokens in custom JSON payloads in our LM Integrations which send to PagerDuty. If there’s changes to the Alert Tokens in a way which would affect how PagerDuty ingests and/or routes the Alerts - and I didn’t know about it to make adjustments -that would really stink, and that’s putting it mildly.) Disregarding that specific page however…. Do people have any ideas on how to track LM website changes in a way that would expose the specific changes? I don’t want to have to resort to ConfigSource monitoring of LogicMonitor’s own website, nor do I want to have to resort to writing a web crawler which would download the entire site and commit it to version control like Github - but I’m tempted, which is sad.31Views2likes4CommentsAnyone using "TextMatch" in a DataSource Datapoint? (without hard-coding the regex)
Is anyone using the "TextMatch" type of Datapoint Post-Processing Interpreter with a Property? https://www.logicmonitor.com/support/logicmodules/datasources/datapoints/normal-datapoints (search on the page for "TextMatch") I'm building a DataSource using SNMP as the Collect method (to try and keep things simple) and I want to be able to parse the full output fromnsExtendOutputFullhttps://www.circitor.fr/Mibs/Html/N/NET-SNMP-EXTEND-MIB.php#nsExtendOutputFullto look for an expected substring. For example if my SNMPd conf entry is extend splunk-status /usr/sbin/service splunk status then I thought I could have a Device Property (or Instance-Level Property) containing the expected "splunkd is running" and then in the Datapoint regex it would be possible to drop in that Property name tokenized like ##TextMatch.substring## Unless I'm mistaken, the only other way I'd be able to post-process text strings like this would be either a Groovy Complex Datapoint, or to completely switch the DataSource over from SNMP Collect to Script and write everything in Groovy (which I could do but I'm hoping to avoid that complexity) Thoughts? Comments? Am I completely out of my mind to be thinking about a Property in a TextMatch Datapoint?76Views1like1CommentRe: Updated Swagger and SDK's
The release notes for v176 just dropped earlier today, and v3 API documentation is mentioned. I don't see the swagger updated yet though. https://www.logicmonitor.com/release-notes/v-176-release-notes LogicMonitor API v3 Release LogicMonitor REST API v3 is now available for use. The REST API Swagger documentation contains 203 frequently used API endpoints. This release also includes a Python SDK file. For more information, seeUsing LogicMonitor’s REST API.5Views0likes0CommentsRe: Docs on "lm.emit" module?
Yep! Indeed it's Groovy script snippets. I also find "lm.emit" as well as "lm.debug" in at least one of the new DataSources for Puppet monitoring. Example:Puppet_Server_JRuby_StatisticslmLocator: TPG9RX // Collector version 30.000 or higher required for script snippets def modLoader try { modLoader = new GroovyShell(getBinding()).parse(com.logicmonitor.mod.Snippets.getLoader()) } catch (ClassNotFoundException|MissingPropertyException ignored) { println "Update collector to version 30.000 or higher for this DataSource." return 1 } def lmEmit = modLoader.load("lm.emit", "0") // Load LM emit module def lmDebug = modLoader.load("lm.debug", "0") // Load LM debug module Then the collect is so simple and elegant.... // Check if status-code is found, if so, convert to raw numeric value. if (statusCodes ){ lmEmit.dp(k,statusCodes ) } else { // print rest of the metrics. lmEmit.dp(k,v) } So beautiful! It's going to be hard to wait for the docs!! ?18Views0likes0Comments
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
