All Activity

This stream auto-updates

  1. Today
  2. Of course, you can always manually create instance groups and sort the items into them manually.
  3. Cloning is one option, but a cleaner option may be to group the instances under that DataSource. It looks like there are several properties that should get discovered by default for every VM instance: 'auto.config.alternate_guest_os_Name': vmConfig?.alternateGuestName, 'auto.config.annotation' : vmConfig?.annotation, 'auto.config.firmware' : vmConfig?.firmware, 'auto.config.guest_os_full_Name' : vmConfig?.guestFullName, 'auto.config.guest_os_id' : vmConfig?.guestId, 'auto.config.managed_by' : vmConfig?.managedBy?.type ?: "false", 'auto.config.modified' : vmConfig?.modified?.getTime(), 'auto.config.template' : vmConfig?.template, 'auto.guest.guest_os_family' : vmGuest?.guestFamily, 'auto.guest.guest_os_full_name' : vmGuest?.guestFullName, 'auto.guest.guest_os_id' : vmGuest?.guestId, 'auto.guest.hostname' : vmGuest?.hostName, 'auto.guest.tools_version' : vmGuest?.toolsVersion, 'auto.guest.tools_version_status' : vmGuest?.toolsVersionStatus2, 'auto.resource_pool' : vm?.resourcePool?.name, 'auto.resource_pool_full_path' : resource_pool_array.reverse().join(' -> '), 'auto.snapshot_count' : vm?.layoutEx?.snapshot?.size(), 'auto.cluster' : esxhost?.parent?.name, 'auto.cluster_full_path' : cluster_path_array.reverse().join(' -> '), 'auto.runtime.host' : esxhost?.name You could group by any of these by simply setting the "Group method" to "Instance Level Property" and then choosing which property to group by. Alternatively, you could choose "Regular Expression" as the Group method and define each group with its own regular expression: For example, if your dev VMs started with "D" and prod VMs started with "P", you would do this: Development="D.*" Production="P.*"
  4. My suggestion would be to clone the DataSource for VM Performance and rename it appropriately for what you are looking for; i.e VMware_vCenter_VMPerformance_DevServers and Displayed as VMware VM Performance - DEV Servers Then you can create a filter that would narrow down only the Dev servers, which I would guess you could do by name with something like ##WILDALIAS## RegExMatch DEV, so it would look for the word "DEV" in every VM name. That would give you a grouping of Developer servers under VM Performance. Cloning the DataSource again and creating a filter that gives you the individual VMs would be the next task. Then you have them grouped, can report on them, and have separate thresholds for them.
  5. Yesterday
  6. I'm not too familiar with it, but i would imagine it's the version number of the API that's available given your current version of Solidfire.
  7. Thanks Michael, Appreciate the follow up and have a good day!
  8. Hi Has anyone experience how argus filter can be used to filter kubernetes namespaces? The example shows how to filter pod, services, deployments.. etc. but not based on namespaces. helm chart config snippet: filters: pod: [] service: [] node: [] deployment: [] hpa: [] Thanks, Joël
  9. Last week
  10. Awesome stuff! Thanks for the contribution @Vitor Santos. These should all be through SR and available in the LM Exchange.
  11. Thanks Stuart and Mike. This all info is helpful for me. Only last question for now, IS FQDN important while configuring LM Collectors? what can be impact post changes domin to LM collectors? Is there and Specific steps needs to take to avoid issue ?
  12. Anymore updates here? Is the Incoming Webhook still the supported method, or is there something newer?
  13. Solidfire user here doing a POC for LogicMonitor. May I get some further instructions on getting this working? The api.version is what I have a question on. This is the first time I need the API version so will you provide info on where to find this? Is there anything on the Solidfire that needs to be done to allow this?
  14. As far as LM is concerned, the identity of the server is tied to the IP address that the Collector uses to monitor it. You can change a lot of things about the device, but as long as the device IP address stays the same, LM will consider it the same device. Discovery will eventually run on the device after you make the change, potentially causing some instances/DataSources to disappear since they no longer apply, and new ones may show up. Depends on the change you make to the device. There are only two things to consider here: reachability and authentication. Unless you're changing the IP address or the network in some way, reachability is unaffected. Authentication is the only thing to keep in mind here. Your Collector defaults to using integrated authentication, meaning that the credentials used to run the Collector service are used to communicate with remote devices. In this case, if some target servers are moved to another domain, you'll need to make sure that the credentials used to run the Collector service still have the requisite permission on those systems in the new domain. This can be accomplished, like @Mike Moniz mentioned, using a trust between the two domains. The other way authentication can happen is if you specify the Windows credentials as properties on the devices in LM. If you do this, the Collector uses those credentials instead of the integrated credentials for access to remote systems. Look at these two support documents: https://www.logicmonitor.com/support/getting-started/advanced-logicmonitor-setup/defining-authentication-credentials and https://www.logicmonitor.com/support/getting-started/advanced-logicmonitor-setup/credentials-for-accessing-remote-windows-computers/
  15. Thanks for the response. So please help confirm if my understanding if for 1 server example 123@abc.com has changed domain to 123@xyz.com, then this 123 host will be not consider as new enrollment ,it will ne the existing monitoring only ? post changing domain , is there any best practices steps for controller. also please consider below one more scenario: there are total 100 server out of which domain migrated for only 50 servers and LM controllers are not part of such migrated list , what can be the issue in this case . will all migrated node monitors continue from LM ( from old Domain)? s any steps that should be too while such domain migration ?
  16. Bumping. Would love the functionality to tune trigger intervals at any level, similar to thresholds.
  17. You could also query the API, to retrieve the data, and return only the largest value.
  18. I don't expect you would lose any history or settings in LogicMonitor. Likely just gaps in monitoring during your migration. LM doesn't talk with AD/LDAP for information so it's not going to just suddenly delete everything. If the Collector is not able to talk with the server for any reasons, it just will keep trying until it can and just have monitoring gaps. You can decommission the server completely and LM will still attempt to gather data until you remove it from LM itself. Is the Collector server also moving domains? I would just restart the Collector services to make sure it can start properly or if it needs it's login credentials updated. If you use SSO with LogicMonitor that might be affected by this domain change, you might want to look into that but I'm not familiar with that part. If you are worried about details or need to complete a full ITIL change ticket or the like, it might be worth talking with LM Support or your rep who I think can look at your specific situation.
  19. Thanks for the response. anyway even if the credentials retain (Like Username and passwords) still domain change needs to handle in crednetials. So what are the impacts of such domain switching activity ? Like , will it loss all gathered OS metrics which were collected before domain switchover ? will all reports affected due to ? in case of domain switch over will added hosts lost from configuration and will it back once after update in domain username password ? please correct my understanding. what are the impacts on collector due to this domain changing ? Sorry in case of any confusion from my side.
  20. Yeah, i've run into this with our fork of the OTel Collector, the config gets overwritten when the installer runs. If a config is provided through a volume mount, i think it errors out. Definitely worth making it an option to pop in your own config files.
  21. I'm going to assume you mean that a Windows system will be changing to another Active Directory domain? The biggest issue likely will be due to credentials. Windows monitoring uses WMI and typically using a local/domain admin account on that system. You want to make sure the credentials either continue working (like if there is trust between domains) or you update the credentials to use the new domain, either on the collector itself if it also changed domain or the wmi.user/wmi.pass properties.
  22. Hi Team, I am enrolling the OS metrics monitoring in LM , we come to know that their might me change in domain name of VM (hostname or IP will be remain as it is ) in next few days, will it affects to this existing monitors ? how will be the behavior and also if same case happened with the controller VM ( same case means - Change in Domain name of hosted VM) then what will be the behavior ? what are the precautions we should take any ideal steps to handle such scenario?
  23. To explain what it looks like in a bit more detail we have a number of boxes running collectors in docker on the same vlan.. They all run keepalived and samplicator, samplicator is bound to 514 and 2055 on each host which then forwards back to the host IP on 1514 and 2056 which i the ports we customised the agent to use. If we take ear down a collector it will find the existing one in portal download it with default config of 2055/514 and obv breaks
  24. We forked it due to some issues with ancient SDK's and many small bugs + needed to add some other dep's (wmic) in the run time and we got persistent mounts for things like netflow (If you crate /usr/local/logicmonitor/bin/netflow and persitent mount it the script says it already installed and refuses which we have a patch for) which it does not support.. Then there is this: - Proxy support broken in offical one it does not honour the proxy settting's passed to the container ONLY for the initial python pull but not the install it self - Netflow ports broken in official one will try bring container up on 2055 we have stuff bound to 2055 that samplicates - Nbar reverts back to disabled - Syslog ports broken same like netflow - Some odd cert issues with the official one due to DNS caching and IP's changing Message me if you want to see what we have done?
  25. Like have another script configured in the datasource that runs whenever you click that button? So for configs, "push config". For the ping DS, you could have a "trace route now" option. For CPU, a "show top processes right now" button. Like that?
  26. What I've always wanted is a user bindable action button on a resource, like the Poll Now button, but configurable so that the datasource bound to the button is based on some applies to logic, configured in settings.
  1. Load more activity