AustinC
NeophyteJoined 5 years ago
User Profile
Neophyte
User Widgets
Contributions
Re: param not found error in datapoint mapping
NaN param not found in output - (method=namevalue, param=.Queue_Name_1) This error leads me to believe you’re specifying something weird in the actual datapoint ‘Interpret output with’ section itself. Can you share a screenshot of an example datapoint and how you’ve specified the parsing strategy? Here is what I might expect this to look like (with ```Queue_name_#```being your ##wildvalue##)31Views1like0CommentsRe: Do you use the focus function in the UIv4 resources tree? Why or why not?
I would use the focus button all the time in UIv3 (mostly because that was the only way to get access to certain functions), but the new UIv4 layout makes me intuit that this focus function may be outmoded. If the button remains, I will echo @Michael Raymond ‘s feedback, that ensuring that this button is always in the same place in a given column would be far more attractive.33Views8likes0CommentsRe: invalid Output format - root element of output JSON should be "data"
Hey, something I recently ran into! Your data is not formatted correctly: BatchScript Data Collection | LogicMonitor Your error is complaining about the fact that your output does not conform to the following format: { data: { instance1: { values: { "key1": value11, "key2": value12 } }, instance2: { values: { "key1": value21, "key2": value22 } } } } At least, I’m about 90% certain that’s what it’s complaining about.15Views2likes0CommentsLM Exchange Use Cases
Can anyone share with me the design intent of LM Exchange? I would like to explore using this as a way of having my users publish LogicModules in our Non-Prod environment that can be easily imported to Production, but I’m intuiting that this is perhaps not an intended use of it. We are presently using the ‘Import from Repository’ functionality, but I know that this is legacy, and understandably a little clunky. That said, it appears that ‘publishing to LM Exchange’ results in my datasources going into Security Review, even though they are ‘Private’ visibility -- this tells me that using this to share LogicModules between my company’s portals is likely not an intended use case. Anyone have thoughts/know anything about this?96Views6likes6CommentsRe: LogicMonitor to ServiceNow Integration (How to pass custom custom parameters)
Does having a space in your property name (##servicenow.monitoring alert##) still resolve to a property? It’s just occurred to me I’ve never tried this, so it might work fine, but I would double check? Also, at the limits of my ServiceNow knowledge, but are you able to view the payloads exactly as they are sent into ServiceNow? I would also attempt to perform the same action LM is doing via a 3rd party API client (e.g. Postman/Insomnia) to see if you are able to figure out whether or not this is an LM payload issue or just not how the Incident API operates?136Views2likes0CommentsRe: LogicMonitor to ServiceNow Integration (How to pass custom custom parameters)
I integrated LM with our Event Management platform, so my experience might not directly translate -- however, looking at the ‘HTTP Delivery’ section of LM’s documentation, I suspect that you may need to add a `category` field to the ‘Alert Data’ part of the integration. String may work, but if it doesn’t, might need to use sys_id if that is a reference field.118Views1like0CommentsRe: How to use the Code Block feature when posting.
Some candid feedback: This is particularly cumbersome. I wouldstronglyprefer to be able to use traditional markdown for these blocks. Slack and Atlassian products are great references for this, as simply typing```creates a free-form code-block field that I can easily copy/paste into. The more time I spend keeping my hands on my keyboard = less time I spend formatting my posts = more time spent on actual Community content :)4Views6likes0CommentsRe: java.lang.NullPointerException on Groovy Collector Attribute script
If you’re not already doing so, I would encourage you to use the Collector Debug Facility. I am nearly certain that your problem is not due to hostProps.get() not working. If `hostProps.get()` fails to find a given property, it will instead return a NullObject class. Here is a test: def testProp = hostProps.get("fake.prop"); println testProp.getClass() Output: class org.codehaus.groovy.runtime.NullObject Here are a few things to look at: If you’re using Collector Debug: You must remember that ‘HostName’ must match the system.hostname property -- NOT the system.displayname property If you’re leveraging Auto-balanced collector groups (ABCGs), you must make certain you are debugging from the collector on which the resource is currently being polled. Validate each one of your variables that you are passing to your HTTP functions This is the most common area that I find problems with my scripting, e.g. a property isn’t being applied at the collector. As an aside, I believe I’ve seen some delays in properties being applied at the portal, but not yet ‘seen’ by the collectors. There is some synchronization that normally has to take place for the collector to become aware of newly-applied-properties. ALL properties are read in as ‘Strings’ by default; your port _might_ need to be cast to an Integer? I don’t think this would result in a NullPointerException, however, as I think that the HTTP class you’re using should be able to cast this appropriately on the fly.8Views0likes0Comments
Groups
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
