Product Discussions | LogicMonitor Community

Discussion

Brad LeClair

Internal Webchecks - Unable to use WebProxy

We have been trying to implement an internal web check using a web proxy (no auth needed) Initially we tried using the groovy script addition of setProxy(String hostname, int port, String schema) eg setProxy(" proxy.test.com ",9090, "HTTP") reference: Executing Internal Web Checks using Groovy Scripts - LogicMonitor No matter what we do the groovy script fails immediately. Then we tried modifying the LogicMonitor configuration file to force LogicMonitor to use the proxy server. Now LogicMonitor communicates out via the proxy --- except the internal web checks which continue to go directly out to the internet. No matter how we try to alter the groovy script it returns: "Error Script did not perform any request at all." Our original generated script that works fine: import static com.logicmonitor.service.groovyapi.PostDataType.*; import static com.logicmonitor.service.groovyapi.StatusCode.*; import com.logicmonitor.service.groovyapi.StatusCode; import com.logicmonitor.service.groovyapi.AuthType; import com.logicmonitor.service.groovyapi.LMRequest; LMRequest request = new LMRequest(); request.useHttp1_1() .followRedirect(true) .needFullpageLoad(true) .get(); return LMHttpClient.request(request); ==================================== Adding proxy command breaks groovy script import static com.logicmonitor.service.groovyapi.PostDataType.*; import static com.logicmonitor.service.groovyapi.StatusCode.*; import com.logicmonitor.service.groovyapi.StatusCode; import com.logicmonitor.service.groovyapi.AuthType; import com.logicmonitor.service.groovyapi.LMRequest; LMRequest request = new LMRequest(); request.useHttp1_1() .followRedirect(true) .needFullpageLoad(true) .setProxy(" proxy.test.com ",9090,"HTTP") .get(); return LMHttpClient.request(request); Any suggestions on how to get an Internal Web Check to work with an internal proxy server?

1 week ago

Discussion

Daniel Blanco

Is there a way to include the Instance Group Name in a report?

Does anyone know if there is a way to include the Instance Group Name as a column in a report? I tried: instance.group / ##INSTANCEGROUP## / system.deviceGroupId but none of these worked. So under any DS you can add an Instance Group and I need to include that Group Name in the inventory report. Its not listed as a property on the Instances INFO page. Thanks,

5 years agolast reply 1 week ago

Discussion

Nick_Ellson

APC ATS Transfer Switches?

Has anyone done a Data Source module for APC ATS Transfer switches? I did not see anything in the published repository..

3 years agolast reply 2 weeks ago

Discussion

Kel L

New module to track Windows versions after patching

Hi, By default, LM doesn't seem to monitor the Build Revision of Windows devices. E.g. It knows something is running Server 2019, but it doesn't know it's running 17636. 9121 . The last four digits are what changes every month when you install updates. I wrote a simple module to grab that information from every Windows device. I also created a Dashboard that you can use to visually see how many devices are up to date and how many are old. I know I could have just put the Build Revision in its own property, but this way the whole thing is in one place. I tried to publish it to the Exchange but apparently that process is broken or something So, I figured I'd just upload it here instead in case anyone is interested. Property Screenshot Dashboard Sample Hmm. Apparently there's no way to upload a file to a post? You'll have to save the text below as a JSON file and then import it I guess. I don't know if all the stuff below is needed, it's just what it gave me when I did an Export. Module { "searchKeywords": "", "integrationMetadata": { "publishedAtMS": 1786125969729, "registryVersion": "1.0.0", "name": "", "checksum": "ce2a6998180cd94967b68b3a93fe0306", "registryId": "e15c5d79-315b-4827-bd45-6a5687174a92", "isPrivate": true, "locator": "3A926C", "lineageId": "tDiDDv3nR8eduyik90gmvg", "status": "SECURITY_REVIEW" }, "name": "Windows_Version_Full", "description": "This module pulls the full Windows Version from a Server or Workstation running Windows 10/2016 or newer. It is stored in the property called auto.os.version.windowsfull.\n\nIt is designed to work with a Dashboard using Resource Explorer widgets filtered on the 3rd octet to visibly see how many devices are on the latest version and how many are behind.", "appliesTo": "iswindows()", "type": 5, "technicalNotes": "", "version": 1786127617, "registryMetadata": { "currentUuid": "tDiDDv3nR8eduyik90gmvg", "originalUuid": "GfnjKuDIR5G9wKib37djPw", "locatorId": "", "registryVersion": "1.0.0", "checksum": "ce2a6998180cd94967b68b3a93fe0306", "namespace": "", "registryId": "", "isChangedFromOrigin": true, "status": "" }, "script": { "type": "powershell", "content": "$computer = \"##HOSTNAME##\"\r\n$Cred = $null\r\n$LMUser = \"##WMI.USER##\"\r\n$LMPass = \"##WMI.PASS##\"\r\n\r\nif ($LMUser -and $LMUser -ne \"\" -and $LMPass -and $LMPass -ne \"\") {\r\n try {\r\n $SecurePass = ConvertTo-SecureString $LMPass -AsPlainText -Force\r\n $Cred = New-Object System.Management.Automation.PSCredential ($LMUser, $SecurePass)\r\n } catch {\r\n Write-Host \"os.version.WindowsFull=Error creating credential: $($_.Exception.Message)\"\r\n exit\r\n }\r\n}\r\n\r\ntry {\r\n\r\n if ($Cred) {\r\n\t\t\t$version = Invoke-Command -ComputerName $computer -Credential $Cred -ScriptBlock {\r\n\t\t\t\t$w = Get-ItemProperty 'HKLM:\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion' -ErrorAction Stop\r\n\r\n\t\t\t\tif ($null -ne $w.CurrentMajorVersionNumber -and $null -ne $w.CurrentMinorVersionNumber) {\r\n\t\t\t\t\t$major = $w.CurrentMajorVersionNumber\r\n\t\t\t\t\t$minor = $w.CurrentMinorVersionNumber\r\n\t\t\t\t}\r\n\t\t\t\telse {\r\n\t\t\t\t\t$cv = [version]$w.CurrentVersion\r\n\t\t\t\t\t$major = $cv.Major\r\n\t\t\t\t\t$minor = $cv.Minor\r\n\t\t\t\t}\r\n\r\n\t\t\t\t$build = if ($w.CurrentBuildNumber) { $w.CurrentBuildNumber } else { $w.CurrentBuild }\r\n\t\t\t\t$ubr = $w.UBR\r\n\t\t\t\t\r\n\t\t\t\t\"{0}.{1}.{2}.{3}\" -f $major, $minor, $build, $ubr\r\n\t\t\t} -ErrorAction Stop\r\n\r\n } else {\r\n\r\n\t\t\t$version = Invoke-Command -ComputerName $computer -ScriptBlock {\r\n\t\t\t\t$w = Get-ItemProperty 'HKLM:\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion' -ErrorAction Stop\r\n\r\n\t\t\t\tif ($null -ne $w.CurrentMajorVersionNumber -and $null -ne $w.CurrentMinorVersionNumber) {\r\n\t\t\t\t\t$major = $w.CurrentMajorVersionNumber\r\n\t\t\t\t\t$minor = $w.CurrentMinorVersionNumber\r\n\t\t\t\t}\r\n\t\t\t\telse {\r\n\t\t\t\t\t$cv = [version]$w.CurrentVersion\r\n\t\t\t\t\t$major = $cv.Major\r\n\t\t\t\t\t$minor = $cv.Minor\r\n\t\t\t\t}\r\n\r\n\t\t\t\t$build = if ($w.CurrentBuildNumber) { $w.CurrentBuildNumber } else { $w.CurrentBuild }\r\n\t\t\t\t$ubr = $w.UBR\r\n\r\n\t\t\t\t\"{0}.{1}.{2}.{3}\" -f $major, $minor, $build, $ubr\r\n\t\t\t} -ErrorAction Stop\r\n }\r\n\r\nWrite-Host \"os.version.WindowsFull=$version\"\r\nexit 0\r\n}\r\ncatch {\r\n Write-Host \"Error: $($_.Exception.Message)\"\r\n exit 1\r\n}" }, "group": "" } Dashboard { "santabaRelease": 243, "defaultDashboardFilters": { "defaultDashboardFilterDetails": [] }, "widgetTokens": [], "name": "Windows Versions (Patching)", "description": "", "overwriteGroupFields": false, "widgetsConfigVersion": 2, "type": "dashboard", "widgets": [ { "position": { "col": 1, "sizex": 10, "row": 1, "sizey": 7 }, "config": { "vizInfo": { "alertFilters": { "datapointsFilterMode": "INCLUDE", "isIgnoreSdtAlerts": true, "datapointFilters": [] }, "groupBy": [ { "name": "auto.os.version.windowsfull", "label": "", "type": "RESOURCE_PROPERTY" } ], "filterBy": { "severityFilters": { "critical": true, "warning": true, "none": true, "error": true }, "filters": [ { "name": "auto.os.version.windowsfull", "label": "", "type": "RESOURCE_PROPERTY", "inclusionType": "INCLUDE", "value": [ { "label": "*14393*", "value": "*14393*" } ] } ] } }, "displaySettings": { "zoomLevel": 100, "showFilter": false, "sortType": "PROPERTY_VALUE_REVERSE", "fontSize": "medium", "visualizationLayout": "HIVE" }, "isSupportCustomProperty": false, "supportCustomProperty": false, "name": "Server 2016", "description": "", "theme": "newBorderGray", "interval": 15, "type": "viz", "timescale": "day", "version": 2, "widgetConfig": "{\"vizInfo\": {\n \"alertFilters\": {\n \"datapointsFilterMode\": \"INCLUDE\",\n \"isIgnoreSdtAlerts\": true,\n \"datapointFilters\": []\n },\n \"groupBy\": [{\n \"name\": \"auto.os.version.windowsfull\",\n \"label\": \"\",\n \"type\": \"RESOURCE_PROPERTY\"\n }],\n \"filterBy\": {\n \"severityFilters\": {\n \"critical\": true,\n \"warning\": true,\n \"none\": true,\n \"error\": true\n },\n \"filters\": [{\n \"name\": \"auto.os.version.windowsfull\",\n \"label\": \"\",\n \"type\": \"RESOURCE_PROPERTY\",\n \"inclusionType\": \"INCLUDE\",\n \"value\": [{\n \"label\": \"*14393*\",\n \"value\": \"*14393*\"\n }]\n }]\n }\n}}" } }, { "position": { "col": 1, "sizex": 10, "row": 8, "sizey": 4 }, "config": { "vizInfo": { "alertFilters": { "datapointsFilterMode": "INCLUDE", "isIgnoreSdtAlerts": true, "datapointFilters": [] }, "groupBy": [ { "name": "auto.os.version.windowsfull", "label": "", "type": "RESOURCE_PROPERTY" } ], "filterBy": { "severityFilters": { "critical": true, "warning": true, "none": true, "error": true }, "filters": [ { "name": "auto.os.version.windowsfull", "label": "", "type": "RESOURCE_PROPERTY", "inclusionType": "INCLUDE", "value": [ { "label": "*17763*", "value": "*17763*" } ] } ] } }, "displaySettings": { "zoomLevel": 100, "showFilter": false, "sortType": "PROPERTY_VALUE_REVERSE", "fontSize": "medium", "visualizationLayout": "HIVE" }, "isSupportCustomProperty": false, "supportCustomProperty": false, "name": "Server 2019", "description": "", "theme": "newBorderGray", "interval": 15, "type": "viz", "timescale": "day", "version": 2, "widgetConfig": "{\"vizInfo\": {\n \"alertFilters\": {\n \"datapointsFilterMode\": \"INCLUDE\",\n \"isIgnoreSdtAlerts\": true,\n \"datapointFilters\": []\n },\n \"groupBy\": [{\n \"name\": \"auto.os.version.windowsfull\",\n \"label\": \"\",\n \"type\": \"RESOURCE_PROPERTY\"\n }],\n \"filterBy\": {\n \"severityFilters\": {\n \"critical\": true,\n \"warning\": true,\n \"none\": true,\n \"error\": true\n },\n \"filters\": [{\n \"name\": \"auto.os.version.windowsfull\",\n \"label\": \"\",\n \"type\": \"RESOURCE_PROPERTY\",\n \"inclusionType\": \"INCLUDE\",\n \"value\": [{\n \"label\": \"*17763*\",\n \"value\": \"*17763*\"\n }]\n }]\n }\n}}" } }, { "position": { "col": 1, "sizex": 10, "row": 12, "sizey": 3 }, "config": { "vizInfo": { "alertFilters": { "datapointsFilterMode": "INCLUDE", "isIgnoreSdtAlerts": true, "datapointFilters": [] }, "groupBy": [ { "name": "auto.os.version.windowsfull", "label": "", "type": "RESOURCE_PROPERTY" } ], "filterBy": { "severityFilters": { "critical": true, "warning": true, "none": true, "error": true }, "filters": [ { "name": "auto.os.version.windowsfull", "label": "", "type": "RESOURCE_PROPERTY", "inclusionType": "INCLUDE", "value": [ { "label": "*20348*", "value": "*20348*" } ] } ] } }, "displaySettings": { "zoomLevel": 100, "showFilter": false, "sortType": "PROPERTY_VALUE_REVERSE", "fontSize": "medium", "visualizationLayout": "HIVE" }, "isSupportCustomProperty": false, "supportCustomProperty": false, "name": "Server 2022", "description": "", "theme": "newBorderGray", "interval": 15, "type": "viz", "timescale": "day", "version": 2, "widgetConfig": "{\"vizInfo\": {\n \"alertFilters\": {\n \"datapointsFilterMode\": \"INCLUDE\",\n \"isIgnoreSdtAlerts\": true,\n \"datapointFilters\": []\n },\n \"groupBy\": [{\n \"name\": \"auto.os.version.windowsfull\",\n \"label\": \"\",\n \"type\": \"RESOURCE_PROPERTY\"\n }],\n \"filterBy\": {\n \"severityFilters\": {\n \"critical\": true,\n \"warning\": true,\n \"none\": true,\n \"error\": true\n },\n \"filters\": [{\n \"name\": \"auto.os.version.windowsfull\",\n \"label\": \"\",\n \"type\": \"RESOURCE_PROPERTY\",\n \"inclusionType\": \"INCLUDE\",\n \"value\": [{\n \"label\": \"*20348*\",\n \"value\": \"*20348*\"\n }]\n }]\n }\n}}" } }, { "position": { "col": 1, "sizex": 10, "row": 15, "sizey": 3 }, "config": { "vizInfo": { "alertFilters": { "datapointsFilterMode": "INCLUDE", "isIgnoreSdtAlerts": true, "datapointFilters": [] }, "groupBy": [ { "name": "auto.os.version.windowsfull", "label": "", "type": "RESOURCE_PROPERTY" } ], "filterBy": { "severityFilters": { "critical": true, "warning": true, "none": true, "error": true }, "filters": [ { "name": "auto.os.version.windowsfull", "label": "", "type": "RESOURCE_PROPERTY", "inclusionType": "INCLUDE", "value": [ { "label": "*26100*", "value": "*26100*" } ] } ] } }, "displaySettings": { "zoomLevel": 100, "showFilter": false, "sortType": "PROPERTY_VALUE_REVERSE", "fontSize": "medium", "visualizationLayout": "HIVE" }, "isSupportCustomProperty": false, "supportCustomProperty": false, "name": "Server 2025", "description": "", "theme": "newBorderGray", "interval": 15, "type": "viz", "timescale": "day", "version": 2, "widgetConfig": "{\"vizInfo\": {\n \"alertFilters\": {\n \"datapointsFilterMode\": \"INCLUDE\",\n \"isIgnoreSdtAlerts\": true,\n \"datapointFilters\": []\n },\n \"groupBy\": [{\n \"name\": \"auto.os.version.windowsfull\",\n \"label\": \"\",\n \"type\": \"RESOURCE_PROPERTY\"\n }],\n \"filterBy\": {\n \"severityFilters\": {\n \"critical\": true,\n \"warning\": true,\n \"none\": true,\n \"error\": true\n },\n \"filters\": [{\n \"name\": \"auto.os.version.windowsfull\",\n \"label\": \"\",\n \"type\": \"RESOURCE_PROPERTY\",\n \"inclusionType\": \"INCLUDE\",\n \"value\": [{\n \"label\": \"*26100*\",\n \"value\": \"*26100*\"\n }]\n }]\n }\n}}" } } ], "version": 2 }

3 weeks ago

Discussion

David Bond

Heads-up: Palo Alto sys_metrics v3.0 breaks the stock Prisma SD-WAN Performance DataSource

TL;DR — On 13 August 2026 at approximately 19:00 UTC , Palo Alto published version 3.0 of the Prisma SD-WAN sys_metrics API, which intentionally changes DiskUsage and MemoryUsage from percentage available to percentage used . The stock LogicMonitor DataSource PaloAlto_Prisma_SDWAN_EdgePerformance computes 100 - value for these two metrics, and auto-selects the highest API version the controller advertises. The result is that every Prisma SD-WAN ION now reports inverted disk and memory figures , with no change on the customer's side. We saw this across an estate of ~525 IONs: roughly 490 devices crossed the DiskUsed alert thresholds within about twenty minutes of each other. If you monitor Prisma SD-WAN with the out-of-the-box modules, you are almost certainly affected right now. The symptom DiskUsed steps to ~95–99% on every ION at once and stays there, tripping the stock > 95 98 99 thresholds. Cpu is unaffected. Two devices, before and after (values from LogicMonitor's own graph data): DeviceTime (UTC)CpuDiskUsedMemoryUsed A13 Aug 15:186.28 2.195 46.30 A13 Aug 18:586.40 97.804 53.68 B13 Aug 15:138.29 1.907 72.65 B13 Aug 19:177.95 98.093 27.18 The before and after values sum to exactly 100. These are complements, not a real change. The part that matters more than the alert noise MemoryUsed is inverted too, and it fails silently in the dangerous direction. Device B above went from a true 72.7% memory used to a reported 27.2%. The disk inversion is loud and obvious — hundreds of alerts and, for anyone with ITSM integration, hundreds of incidents. The memory inversion is the opposite: a device under genuine memory pressure now reports plenty of headroom and will not alert . Anyone who has been running inverted since 13 August has had no working memory alerting on their SD-WAN edge estate, and nothing in the UI would tell them. If you are affected, it is worth reviewing that window specifically, not just clearing the disk alerts. Root cause — Palo Alto documents this themselves This is an intentional, documented breaking change , not a Palo Alto bug, and it will not be reverted. From Palo Alto's public OpenAPI specification ( open_api_unified.json , also rendered on pan.dev ), path /sdwan/monitor/v3.0/api/monitor/sys_metrics : Behavior change in 3.0: DiskUsage and MemoryUsage report the percentage used ; versions 2.0 – 2.4 reported the percentage available . CPUUsage min and max are corrected; earlier versions returned them swapped. Supported metrics are unchanged from 2.4. The same change re-labelled the previous version. Path /sdwan/monitor/v2.4/api/monitor/sys_metrics : Deprecated behaviour. DiskUsage and MemoryUsage report the percentage available , not used, and CPUUsage returns min and max swapped. Version 3.0 corrects all three. Timing lines up exactly. The spec commit introducing v3.0 is dated 2026-08-14T06:02:17Z ; the previous revision (2026-08-07) contains no v3.0 and no deprecation note. The API changed on the 13th and the documentation synced the following morning. The same commit applies the identical change to the legacy CloudGenix-style spec, so both API styles are affected. Why it reached everyone with no configuration change The stock collection script selects the highest API version the controller advertises: String sysMetricsVersion = prismaSnippet.sanitizeVersion( hostProps.get("auto.paloalto.prisma.sdwan.apiversion.sys_metrics_monitor")) ?.split(",")?.max() ?: "2.0" The moment 3.0 appeared in the auto-discovered list — ours now reads 2.0,2.1,2.2,2.3,2.4,3.0 — every collector silently moved from v2.4 to v3.0, while the DataSource carried on applying the v2.4-era correction: if (dpName == "DiskUsage" || dpName == "MemoryUsage") { lmEmit.dp(dpName, dpAvg ? (100-dpAvg) : 0) } else { lmEmit.dp(dpName, dpAvg) } An inversion designed for "available" applied to a value that is now "used". That is the entire fault. Scope — which modules are affected We checked all four stock Prisma SD-WAN DataSources. Only one carries the inversion: ModuleLocatorVersionUses sys_metrics ?Has 100 - x ? PaloAlto_Prisma_SDWAN_EdgePerformance2C69WT 1.2.0 YesYes — affected PaloAlto_Prisma_SDWAN_EdgeHealthFL44YM 1.6.0NoNo PaloAlto_Prisma_SDWAN_UnderlayLN6GNG 1.6.0NoNo PaloAlto_Prisma_SDWAN_OverlayCCP494 1.3.0NoNo The fix we applied, and how we verified it We removed the inversion so the script emits the API value unchanged, keeping v3.0. A Poll Now immediately afterwards on device A returned: Cpu = 6.625 DiskUsed = 2.196 MemoryUsed = 46.326 Those land on the pre-13-August values to three decimal places. That is what makes this conclusive rather than merely plausible: removing the inversion restores continuity with the historic series and correct alerting, which is only possible if the API semantics were what Palo Alto says they are. We do not recommend pinning back to v2.4 as a long-term answer. It is now formally deprecated, and Palo Alto deleted v2.3 from the spec in this very same commit — pinned versions here have a limited shelf life. What we think LogicMonitor needs to do Posting this openly because the fix belongs in the module, not in every customer's portal — and because affected customers are alerting right now . 1. Correct PaloAlto_Prisma_SDWAN_EdgePerformance ( 2C69WT ). Ideally make the transformation version-aware rather than simply deleting it, since the correct behaviour genuinely differs by API version: // invert only for the deprecated versions that report "available" boolean reportsAvailable = (sysMetricsVersion in ["2.0","2.1","2.2","2.3","2.4"]) if (reportsAvailable && (dpName == "DiskUsage" || dpName == "MemoryUsage")) { lmEmit.dp(dpName, dpAvg ? (100 - dpAvg) : 0) } else { lmEmit.dp(dpName, dpAvg) } That keeps working for any customer still pinned to an older version, and is correct on v3.0. 2. Check the CPUUsage min/max correction. Palo Alto's note says v3.0 also fixes min and max being returned swapped. If the paloalto.prismasdwan snippet requests a min or max statistic, the meaning of Cpu has changed too. Our Cpu values moved only slightly, so we cannot tell from the outside — but you can, and the datapoint is described as "Maximum percent CPU utilization". 3. Fix the version-selection logic across all four Prisma modules. ?.split(",")?.max() is a string comparison, used at 11 call sites across the four DataSources. It is already wrong today, independently of this incident: auto.paloalto.prisma.sdwan.apiversion.waninterfaces currently advertises 2.1 … 2.9,2.10 , and string-max returns "2.9" , not "2.10" . It needs a numeric version comparison. 4. Reconsider auto-adopting the maximum advertised version at all. Taking whatever the vendor publishes means a documented breaking change becomes a silent data-correctness incident in every customer portal simultaneously, at a time of the vendor's choosing. Pinning modules to a validated version, and treating a newly advertised version as something to review rather than adopt, would have contained this entirely. 5. Please proactively contact customers monitoring Prisma SD-WAN. This is the important one. Every customer using the stock module is affected, the disk alerting is noisy enough to be self-evident, but the memory under-reporting is silent and will not be noticed . Customers cannot reasonably be expected to discover this themselves — the numbers look plausible, nothing errors, and the module is behaving exactly as written. A known-issue entry plus a targeted notification to Prisma SD-WAN customers would save a lot of people a confusing morning, and would close the memory-alerting gap before someone finds it the hard way.

Aug 14, 2026 at 11:06 AMlast reply 3 weeks ago

Discussion

Troy Frommer

LogicModule for Pure Flash Blade

LogicModule

Greetings LM Community, I wanted to reach out to ask if anyone has created a custom module for connecting to a Pure Flash Blade. There is an official module for Pure Flash Array but these are different and to this point I have not had any luck in connecting to the Flash Blade endpoint by using similar methods. Thank you for the help, Troy

3 weeks ago

Discussion

Justin Allen

Monitoring Infoblox DDI Bloxone without a Grid

So most of the Infoblox modules I've found seem to rely heavily on SNMP which is great, SNMP is alive and well. However, if you purchase an Infoblox solution without the monitoring module/license SNMP is not supported directly on the DDI appliances themselves, to my knowledge. I actually opened a support case with Infoblox as was told SNMP was not supported on their Data Connector and can't find the nerd knobs for the DDI appliances themselves. I've created resources for them in LM and obtained local access to the DDI appliances but there's no place to associate an SNMP user within the Infoblox csp portal. After banging my head against that for a while, I switched my thoughts toward an API integration which works decently for some base level DHCP metrics but isn't as stalwart as I'd like. I was able to couple a feeble API integration along with syslog collection over TLS, having the requirement to install a syslog engine on my collector that could listen on TCP 6514, and get more metrics such as DHCP discover rates etc. Has anyone else found a stable solution for monitoring an Infoblox solution that does not include a Grid or Grid Master with modules for maybe SNMP and API that they like? I feel like I'm a bit between a rock and a hard place with the limitations imposed by Infoblox on what they support. I'm happy to share the custom data sources I created to get to where I am but wanted to get some feedback first.

3 weeks ago

Discussion

Kel L

Any way to find any module instances that are Not Collecting?

Hi, I stumbled on a server that had its Collecting toggled off for it Memory Usage. It should have had alerting turned off, but should have still been set to collecting. That got me wondering if I have any other devices where someone had turned COllecting off instead of only turned off Alerting. I looked around and didn't find any way to do this. I checked with Support and was told I could try an API call. I used the Powershell Modules and found that the only way to this is to get a list of all my devices (a few thousand of them). Then pull a list of all the modules that are associated with each device. Then loop through the list and check the StopMonitoring property for each module and see if it's set to True. Each of these calls takes 1-2 seconds. Each device generally has 80-100 module that Applies To finds. I have thousands devices. Add that up, and my script will take a week or more to run and figure this out. Does anyone know of a better way to find this information? I was hoping for a simple Not Collecting report or something that would be quick and easy since I'd think everyone would want to know if they had things Not Collecting any data. Thanks.

1 month agolast reply 1 month ago

Discussion

Justin Lanoue

Handling Alert Storms?

Good morning, Just wanted to put this out there to see how everyone else is handling these types of situations. Scenario: Switch goes offline. Alerts that generate: BGP Alerts x5 OSPF Neighbor Alerts x5 Interface alerts x10 Uptime alert when it comes back online Maybe a syslog event Problem: With that being said, how does your team know that all these alerts were related and should be bundled into the Switch going offline alert as the parent ticket? Maybe it's a portal issue on our end but like OSPF Neighbors when clicking on them doing even topology map to the others... Same with BGP. You can't dependent alert map instance alerts, only resources which is useless here. I could maybe configure cluster alerts when more than 1 or 2 alerts of the same type generate but it can't be specifically grouped to pick and choose which instances. Services don't really cut it as they don't suppress the individual alerts so at this point is my best bet to just document what alerts when the switch goes down and apply that to the offline alert of the switch or maybe look into better topology mapping so it's clearer?

8 months agolast reply 1 month ago

Discussion

Dalton Woolsey

BGP Peers & Alerting for Multiple Sites

Community, Has anyone else experienced a BGP Alert storm when one BGP Peer blips? We have a full-mesh environment (rather than Hub & Spoke), so when one BGP Peer flaps, we get an alert from each site's BGP router. What have folks done to mitigate the BGP Alert storm in this scenario? Thanks, Dalton

1 month ago

Discussion

Bram Assendorp

Netflow v9 - The collector has not reported any traffic flow health metrics for this device.

Anyone got Netflow working with Cisco equipment? Got the following config: flow record NETFLOW-RECORD-LM description NetFlow record format to send to LM match ipv4 source address match ipv4 destination address match transport source-port match transport destination-port match ipv4 protocol match interface input match datalink mac source address input match datalink mac destination address input match ipv4 ttl match ipv4 tos collect interface output collect timestamp sys-uptime first collect timestamp sys-uptime last collect flow direction collect counter bytes long collect counter packets long collect timestamp absolute first collect timestamp absolute last flow exporter LM1 destination xxx.xxx.xxx.55 source TenGigabitEthernet0/1/1 transport udp 2055 template data timeout 60 flow monitor NETFLOW-MONITOR exporter LM1 cache timeout active 60 record NETFLOW-RECORD-LM interface gi0/0/4 ip flow monitor NETFLOW-MONITOR input ip flow monitor NETFLOW-MONITOR output interface TenGigabitEthernet0/1/1 ip address xxx.xxxx.xxx.131 255.255.255.248 negotiation auto end But still nothing in Logicmonitor, tested with Wireshark, and it does receive netflow on port 2055. $ !netflow func=listdevices ID Name Interface Indx IP Addresses ======== =================== ============== ======================== 2626 xxx.xxx.xxx.167 xxx.xxx.xxx.131 And yes, netflow is enabled on device level, and interfaces are visible an other monitoring works great. It just seems, LM is not processing any info.

1 month agolast reply 1 month ago

Discussion

BH IT

monitoring MS SQL 2025

anyone able to get this to work? none of the datasources work with either integrated or local accounts. i see this is not on supported list for SQL. any idea when its coming? sql server 2025 came out over 6 months ago...

2 months agolast reply 1 month ago