Search the Community

Showing results for tags 'vmware'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • From LogicMonitor
    • General Announcements
    • LM Staff Contributions
    • Community Events
  • LogicMonitor Product Discussion
    • Feature Requests
    • LM Exchange
    • Ask the Community

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 15 results

  1. Has anyone had any luck monitoring VMStatus for reboots without using the DaysSinceLastReboot? as this gives a false reading, as it kicks in when the VM is vMotioned. I have tried the GuestState but it looks like the GuestOS isnt in the state for long enough for that to trigger
  2. We would like the ability to generate alarm on events generated within the vSphere event log, I really can't believe this isn't in place already.
  3. Does anyone have a good datasource they are using for monitoring key services on a VMware vSphere ESXi host - e.g. hostd, vpxa, vpxd, mgmt-vmware, etc? Thanks Will
  4. Hello, I'm new to LogicMonitor and we've just got our first vCenter server configured and monitored. I'm trying to figure out why the VMware Virtual Machine Status dashboard is saying "Instance limit exceeded (2000) (other than the obvious - that we exceeded the limit) and how to modify the dashboard to provide some meaningful data and visualizations that we can use. Has anyone else encountered this? And if so do you have a smaller query or dashboard panel that can help correct this? Thanks in advance.
  5. We were running into an issue where disks were not consolidating properly following our backup completing, we are using Veeam with VMware. Since this wasn't included our of the box I have updated the default datasource to include a consolidationNeeded graph and datapoint. consolidationNeeded - Whether any disk of the virtual machine requires consolidation. This can happen for example when a snapshot is deleted but its associated disk is not committed back to the base disk. (https://code.vmware.com/apis/358#/doc/vim.vm.RuntimeInfo.html) This can cause a problem with performance as it wil
  6. Hi, I just got done working with VMware support on an issue where our ESXi 6.5 hostd process would crash during a booting phase. We eventually traced it back to a bug in some vSAN code that LM monitoring is polling.. It doesn't matter if you're running vSAN in your environment or not. Our work around has been to disable host level monitoring in LM for our ESXi hosts for now and it's been stable ever since. The expected fix is scheduled for release in Q3 2018 from VMware.
  7. Previous versions of VMware datasources had the ability to monitor disk space for VMs via vCenter. Looks like this ability has disappeared after LM fixed a datasource bug in January. We now have 100+ VMs that we monitor via vCenter but no alerts for their disk space. Is this something we are missing by accident, or has LM stripped this functionality on purpose?
  8. VMware "In­-Guest" DataSources - Version 1.0 - LogicMonitor Custom Development Summary: The following provides information and deployment instructions for the application of hypervisor-­level monitoring data - as presented within a Windows virtual machine in LogicMonitor. There are three "In­Guest" VMware DataSources ­- they are: VMware_vSphere_VMperformance_InGuest (locator code: CHLF7C ) VMware_vSphere_VMsnapshots_InGuest (locator code: 9YF42D ) VMware_vSphere_VMstatus_InGuest (locator code: ZMEJ6P ) How it Works: These datasources were cloned from the official
  9. Is there a an LM Exhange module similar to/ or a variation of the one below which can alert for VMs if they go offline as long as their properties are tagged with a certain keyword? We have had instances where running VMs go offline but LM does not alert, because of this particular filter. Lookign for a simple module to only alert if VM is down based ona vm tag we can set.
  10. The Windows EventSources monitoring has been very useful for us, and we were hoping to be able to replicate the same with vSphere's logging (vCenter, vpxd, etc). Right now our only alternative is leveraging VMware's "Log Insight" tool, but we were hoping to have this integrated into LogicMonitor so we're not duplicating monitoring across separate monitoring tools.
  11. We have all of our VMs monitored with LogicMonitor which does a good job gathering details from our VMs. However, we have VMware tools installed on all VMs and leave WMI Performance Logging enabled. This VMware tools feature ends up generating a ton of events: 256 and 258 which reference vmGuestLibrary vmStatsProvider alerts. This is just standard behavior of VMware tools since it is pulling logging details in and creates these events. What I am trying to determine is if I can safely disable this WMI performance logging and allow LogicMonitor to still do the WMI calls, and if there is any
  12. I would love to see the "ESX VM" datasource allow grouping its instances by the VDC/Resource Pool in which each VM is contained. Use case: Each VDC in our infrastructure may have different alerting rules. We have many VDCs and most of these VDCs are available directly to customers through vcloud director, allowing them to create their own VMs using names over which we have no control (so we can't use the automated name filters to group them). Customers may add a new VM at any time within their own VDC and they have the option to expand out at will without notifying us. Currently, grouping
  13. Need support for IPFIX flows coming out of VMWARE v10. v10 does not use v5 or 9 flows.
  14. These are some simple troubleshooting steps I use when dealing with ESX servers. LogicMonitor has debug tools that can be run in the debug window on the collector the ESX currently assigned collector. The first useful tool is !http. This simply sends a HTTP request to a host and print the response. The ESX API has a few pages we can use that DOES NOT require authentication. This is helpful to test a connection outside of credential issues. For example the below debug command returns “The Web Services Description Language (WSDL) file containing definition of the VMware Infrastructur
  15. There are quite a few datasources that require direct access to ESXi hosts when the data is readily available in vCenter. This is painful since establishing permissions to hosts in most environments is tricky at best (confirmed after extended testing done yesterday) and the documentation provided is not complete. The problem is if you just point current DS definitions to vCenter (e.g., hardware), data is acquired, but the DS has no per-host data, it just grabs the data for one host and displays it in that subtree.