James_Rolt
Joined 4 years ago
User Profile
User Widgets
Contributions
Change Instance Name
Hi, I have noticed a few alerts are not generating ticket within our Connectwise Manage via the integration, looking in the log i can see a 400 error with the below payload: { "code": "InvalidObject", "message": "ticket object is invalid", "errors": [ { "code": "MaxLengthField", "message": "The field summary must be a string with a maximum length of 100.", "resource": "ticket", "field": "summary" } ] } I understand that the length restriction will be from connectwise, but is there a way to change the name of an instance within logicmonitor. The alert in question here will be around 104 characters in length. The instance for this is picked up via auto discovery from Unifi Access Point Datasource and i cannot see a way to change the name of this. Thanks, JamesSolved178Views10likes3CommentsRe: Citrix Cloud Monitoring
Hi, Has anyone had any issues with the datasources recently, whenever i do a poll now on any of the datasources i get the below error. Is anyone aware if the service URL has changed? Thanks, James The script failed, elapsed time: 3 seconds - Unable to determine the current character, it is not a string, number, array, or objectThe current character read is 'A' with an int value of 65Unable to determine the current character, it is not a string, number, array, or objectline number 1index number 0Access denied to query Monitor objects : Invalid Service URL^groovy.json.JsonException: Unable to determine the current character, it is not a string, number, array, or objectThe current character read is 'A' with an int value of 65Unable to determine the current character, it is not a string, number, array, or objectline number 1index number 0Access denied to query Monitor objects : Invalid Service URL^ at groovy.json.internal.JsonParserCharArray.decodeValueInternal(JsonParserCharArray.java:206) at groovy.json.internal.JsonParserCharArray.decodeValue(JsonParserCharArray.java:157) at groovy.json.internal.JsonParserCharArray.decodeFromChars(JsonParserCharArray.java:46) at groovy.json.internal.JsonParserCharArray.parse(JsonParserCharArray.java:384) at groovy.json.internal.BaseJsonParser.parse(BaseJsonParser.java:112) at groovy.json.JsonSlurper.parseText(JsonSlurper.java:205) at groovy.json.JsonSlurper$parseText.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:128) at Script2.getCitrixData(Script2.groovy:71) at Script2$getCitrixData.callCurrent(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:51) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:157) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:177) at Script2.run(Script2.groovy:36)31Views3likes0CommentsRe: Dynamic Thresholds
16 minutes ago, Stuart Weenig said: The dynamic threshold visualization isn't smart enough to know that the metric can't/won't go above 100%. It's just calculating what the expected value might be based on historical norms. I'd lengthen the timeframe that you're looking at to get a better idea of what the algorithm thinks compared to actual values. You're right though, this particular CPU seems to run hot, so a dynamic threshold would consider 100% utilization "normal". Remember, dynamic thresholds don't tell you what's good vs. what's bad. They tell you what's "normal" vs. "abnormal". If this server normally fluctuates between 50% and 100% all the time, then a current value of 99.9% would be considered "normal" and wouldn't trigger an alert. Ah ok, so in this case with CPU usage, it would be best to have it at a static threshold, that may need to be tuned per instance to a level to reduce noise Thanks26Views0likes0CommentsDynamic Thresholds
Hi, I am looking at setting up dynamic thresholds for the following datasource and datapoint: Datasource - VMware_vCenter_VMPerformance Datapoint - CpuUsagePercent With the idea that if a VM in our VCenter enviroment goes above the normal level it would alert. I have currently setup an instance group and added the required instances into this (We dont want it on all VMs) but looking at the custom settings for some of the VMs the graph is above the 100% limit (example below) So how would this alert, as the metric would only go up to 100% CPU Usage at a max. Thank you, James122Views1like3CommentsRe: Citrix Cloud Monitoring
Hi, It is currently collecting data, but the citrix cloud machines DS is missing around 30 devices. AD is working for the devices but the missing ones are been filtered out as deleted (when on citrix cloud they are not deleted and are in production) I have not made any changes but the groovy scripts for Active discovery is currently set to the below which does not match yours Collector Attributes Groovy Script Thanks, James 1 hour ago, Vitor Santos said: Hey James, Is it actually grabbing data currently (if you test the AD for example)? I've noticed that from those DS we need to change some code (due to API changes) - as mentioned by Brian Wagner in this thread... This is what I've changed on ours: here using the 'api-eu' endpoint as an example. From there it should work... if you did this already, disregard my message :)/emoticons/smile@2x.png 2x" title=":)" width="20" />0Views0likes0CommentsRe: Citrix Cloud Monitoring
Also jumping back onto this! I have managed to get the datasource setup and was working perfectly, but recently i have noticed that within the 'Citrix Cloud Machines' Datasource multiple machines are missing from the list. I have recreated the accounts ect but still seeing the same machines. Has anyone else had this issue, or is this a configuration within Citrix Cloud? Any help would be great! Thanks17Views0likes0CommentsRe: Zerto JobStats
On 2/11/2020 at 4:58 PM, Joe Williams said: Use the 6477DR code in the LM Exchange. It pulls everything down. I used it and heavily modified it to monitor via VPG instead of VM as each VM is forced to have the same RPO/Status. Hi, Have you got the details on how you modified this to report on the VPG instead please? Thank you, James21Views0likes0Comments