NBM
Joined 7 years ago
User Profile
User Widgets
Contributions
VMware Overview Dashboard
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 theVMware 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.17Views0likes2CommentsRe: event handlers
1 hour ago, mnagel said: One possibility would be to create datasources that don't actually collect data, but do the check and repair operation, with a datapoint as a side effect. Also, is this something that you've actually tested and implemented out of curiosity of just an idea. Thank you for the feedback as well.3Views0likes0CommentsRe: event handlers
39 minutes ago, mnagel said: Alert processing happens outside the detection point (in "the cloud")-- there need to be triggers to an event handler that operatein the collector context. That makes complete sense and something I initially overlooked as in the context of a server, LM needs to push logic down the to collector (not sure what that process is called) and then the collector needs to push that down to the server and then send those results back up to the cloud via the collector for processing. In the context of the "check" I'd like to see some type of functionality that would look something like this: From the cloud run a Windows service check through the collector down the server If the service has failed, execute trigger (in the same workflow) to attempt to restart service, and if service restarts, do not alert, but send those results back up to the cloud for processing If the restart fails, do the same thing sending the results back up to the cloud with the difference being generate an alert. I'm also curious how long this feature request has been asked for since during our demo LM stated they had plenty of customers asking for this functionality.3Views0likes0CommentsRe: event handlers
I'm cross-posting this as I saw the link to this thread in the other post I made, so apologies for the duplicate: Hello, We're currently looking to evaluate LogicMonitor as a potential replacement for Microsoft System Center Operations Manager (SCOM) and prior to SCOM being our enterprise monitoring toolwe had IBM Tivoli Monitoring (ITM) in place within our organization. So we come from well over 10+ years of being able to take corrective actions without the tools themselves in response to various alerts that are raised and based on our initial demo with the LogicMonitor team, we understand that's not a feature of the product as they don't want to be in config management business which I understand. However, we can't be the only organization that has this issue so I'm curious how others have worked around this that would be willing to share their solutions. Here are some simple things we do today: 1. Windows Service Restarts (we only alert in most cases if the corrective restart action fails) 2. Linux Process Counts (we'll attempt to restart the process or execute some type of other scripted action) 3. IIS Application Pool failures (we'll attempt using builtin Windows functionality to recycle and AppPool) Appreciate the responses, thanks!3Views0likes0CommentsRe: LM "Actions"
Hello, We're currently looking to evaluate LogicMonitor as a potential replacement for Microsoft System Center Operations Manager (SCOM) and prior to SCOM being our enterprise monitoring toolwe had IBM Tivoli Monitoring (ITM) in place within our organization. So we come from well over 10+ years of being able to take corrective actions without the tools themselves in response to various alerts that are raised and based on our initial demo with the LogicMonitor team, we understand that's not a feature of the product as they don't want to be in config management business which I understand. However, we can't be the only organization that has this issue so I'm curious how others have worked around this that would be willing to share their solutions. Here are some simple things we do today: 1. Windows Service Restarts (we only alert in most cases if the corrective restart action fails) 2. Linux Process Counts (we'll attempt to restart the process or execute some type of other scripted action) 3. IIS Application Pool failures (we'll attempt using builtin Windows functionality to recycle and AppPool) Appreciate the responses, thanks!7Views0likes0Comments