Search the Community

Showing results for tags 'Collector'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • From LogicMonitor
    • Product 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

  1. Is it possible from the debug console to reboot the collector box? If so what command can I use to do this? TIA..
  2. A while back I published some very simple ConfigSources to monitor your collector .conf files: https://communities.logicmonitor.com/topic/1345-collector-configsources/ Here's an adaptation that writes the various collected configs to a dashboard, writing each of the config outputs to a text widget. Notes: THIS IS A PROOF OF CONCEPT. No warranty is given or implied (value of your investments may go down as well as up, check with your health professional before taking this medicine, etc). Please test before deploying! As with all data within LogicMonitor (or any system),
  3. A couple of choices of ConfigSource to monitor the .conf files of your collectors. Note these are two versions of the same thing - you do not need both. One explicitly monitors only the four key .conf files; agent.conf, sbproxy.conf, watchdog.conf, wrapper.conf. That's done via the Active Discover script simply printing those four known filenames as instances: 76PEZ2 (v1.2) The other version has a more involved Active Discovery that lists any .conf found in the Collector config folder, with the exception of 'persistent_task.conf' as this file is continually being updated. T
  4. I would like to see a prompt for SDT that when I specify "[location].All" LM asks if I would like to place the Collector in SDT. I would never think to look in "Settings" area to place the collector in SDT, or that when I specify "All" the collector is not included. I understand why it separate, but the location for SDT on the collectors is not intuitive. I naturally went to [Domain].Collectors, which was incorrect, after I was told the collector SDT is separate. Thanks
  5. Hi All, As we all know, that currently logic monitor has a feature to setup only 1 fail over collector. I would like to request for a feature, where we can have multiple fail-over collectors and in such a way that even if, the collector is active and polling objects, it still can be set as a fail-over collector. Thanks & Regards, Akash Pandya
  6. Windows Server Core and (the free) Hyper-V Server Core are GUI-less versions of Windows that can be administered remotely with GUI tools. We've recently seen an uptick in requests for deployment of the collector to these platforms, as Windows introduces a lot of overhead with the addition of the GUI; the other compelling reason to go this route being that Hyper-V Core is a free license of Windows from Microsoft (similar to the free flavor of ESXi, only it can run a Windows collector!) Microsoft Documentation: Managing a Server Core Server Configure Server Core with the SConfi
  7. I know that it is not exactly recommended/reliable to use a 1GB/1CPU Core machine to monitor...but it seems that installing a "nano" sized collector on a t2.micro AWS instance and having it just monitor itself brings the AWS instance to a screeching halt. I am seeing that when the collector is running, top shows that CPU pegs to 100% almost nonstop. Memory is not hit quite as bad..but it does get up there to use 500mb+ But the CPU load average is 5+ cores and it makes the system unusable. Sometimes this causes the instance to throw status alerts & even crash. Question: Has a
  8. Exporting Netflow from Windows with FlowTraq Exporter NetFlow is an industry standard network protocol for monitoring traffic flows across a network interface. It is used most commonly by devices like firewalls, routers, and switches, but some software packages make it possible to export Netflow data from a server operating system - in this case Windows - to a Netflow collector (LogicMonitor) for traffic analysis. Instructions 1.) Register for and download the free FlowTraq Exporter. 2.) Download WinPcap (Windows packet capture library). 3.) Install WinPcap on the serv
  9. Just in case this helps other customers... SYMPTOMS: The Windows collector installed ok and the two Collector services were running but the collector could not finish the verification/registration step and showing the 'flame alert' on Settings > Collectors screen. After some troubleshooting, we looked in the wrapper.log file on the collector and saw this error message: [MSG] [CRITICAL] [main::controller:main] [AgentHttpService.checkCertificateOrWait2Valid:1029] The santaba server is not trusted, and "EnforceLogicMonitorSSL" is enabled. Wait 1 minute to retry. Please check the ne
  10. I would like the REST API to support Scheduling a collector version update Applying a one-time collector version update Working with the Collector Custom Properties (recently added I think, but don't see anything in the online documentation about support in REST API).
  11. Collector groups were added recently, and are detailed here: https://communities.logicmonitor.com/topic/637-collectors Now let's expand upon that functionality...What if collectors be grouped dynamically? Identically to how Devices dynamic groups work, could I assign properties to collectors, then build dynamic groups based from the properties? Ways that envision sorting collectors: Production/test, primary/backup, collector number (1-99, 100-199, 200-299, etc.), zip code, time zone, alphabetical. In each of these cases, this would give full flexibility on how collector upgrades ar
  12. Hi I am having a frustrating experience when I have tried to make LM redundant using multiple collectors, but then I am at the mercy of the customers internet connection so when the collectors go down, I then get a couple of thousand host status events rather than a number of critical collector alerts making it very hard to see the wood for the trees in the UI alerts page as I cannot just filter out host status alerts as I could have more from other customers. Am I missing something? Do others have a decent scalable workaround? Has this been raised as a feature request befo
  13. Has anyone else experienced any issues with Collector 27.002? I updated our SNMP collector (8G RAM, about 600 devices) a few days ago and twice it has gone down with memory maxing out. Have downgraded back to 27.000. I did a Send Logs to LogicMonitor, if it helps.
  14. I know I've brought this up before, but I'd like to bring it up again. LM's requirement that collectors run as local admins (or system) is a GAPING security hole in your product. No amount of certificate signing, or other like security measures are a replacement for running a collector or an agent as a read only account. The fact is, with every security measure you take, if the collector is running as an admin account or a system account, its going to be exploitable in one way or another. Having the signed scripts and what not, would be great, but really it shouldn't be the primary focus I
  15. Hi, Maybe the community are intressted in using collectors as stand-alone outside a domain (in a workgroup).. We are and have ran into all possible effects of it... one thing is to monitor Windows DHCP Servers that ar joined to a domain. THen you need to authenticate against some classes to discover and to get metrics. Had some chat sessions with the LM support and they got me closer to the solution.. But I solved it finally using credentials to discover and inventory the DHCP server and Scopes with powershell using domain credentials on my collector in a workgroup Here they Are
  16. These are not ConfigSources. They do not record, store, alert on changes to, let you view historic (etc) config files. If that's what you're after and you have LM Config, take a look here: https://communities.logicmonitor.com/topic/1345-collector-configsources/ These, however, are DataSources that read and parse out certain values from certain Collector .conf files, that let you quickly see a few key settings without having to look at and scroll through the config files. Graphs can show you how values have been changed over time. Mostly these are for information only, although there
  17. New to this forum. We are trialing LogicMonitor as a replacement for a traditional NMS system. We're a resell of NMS service. I believe the industry calls that an MSP. We want to resell this service using an appliance as collector. Basically we want to preload the collector software and send it to a customer location and then go from there. What I'm struggling with is some guide to what hardware we should spec out for this. I realize a one size fits all is not going to get it. Our customers service is all WAN only routers and some customers have netflow. We have some customers that ha
  18. Ability to filter !tlist output. Example, !tlist all data points not returning any data aka nan.
  19. This article provides information on High CPU usage on the Collector . (1) General Best Practices (a) First and foremost we advise our customers to be on latest General Release Collectors (unless advised not to) . Further information all the Collector information could be retrieved on the link below : https://www.logicmonitor.com/support/settings/collectors/collector-versions/ Also on the release notes of each newer Collector version we will indicate if we have fixed any known issues : https://www.logicmonitor.com/releasenotes/ (b) Please also view our Collector
  20. Has anybody downloaded a valid collector executable for windows using the rest API? I tried both python and powershell code to download, but the file downloaded cannot be executed. Logic Monitor Support has confirmed that this is a bug and they are working on it. Request #77831
  21. Let’s walk through the attached Python script that utilizes the LogicMonitor API. This script will automate a collector install for Linux. It will Create the Collector Object, Download the collector installer, give the collector executable permissions, and finally install and register the collector. Full documentation including examples for the LogicMonitor REST API can be fond in the below link https://www.logicmonitor.com/support/rest-api-developers-guide/ We have examples for most of the functions in the API on our support site. Using these examples, it’s possible
  22. LM Team, When you are on your primary collector and choose a failover collector and are deciding to check that box "Automatically failback when THIS collector becomes available again". The way that it is worded, THIS collector could mean the current collector you are configuring. Then again, the checkbox is underneath the failover collector you just selected and it is indented, so it's easy to convince yourself that it could be referring to the failover collector. I think it would be worth re-wording or at least offering a hover-hint (?) box to clarify that the failback will be occur
  23. Collectors can be installed using Nano/Small/Medium/Large configurations. Please add a column in Settings->Collectors to show this.
  24. Hi All, Could you please consider the following as product feature. To make changes to the "Configure LogicMonitor Collector" without the need to uninstall and reinstall the collector. For example the error stating that your credential is wrong no you need to schedule down time just to uninstall and reinstall the collector where you can just simply modify your credential which take you 5 sec to do. Thank you! Looking forward to the out come. Kind Regards Gerrit
  25. I understand that at this moment we can only receive LM Collector update notifications by subscribing to https://www.logicmonitor.com/releasenotes/ which then sends an email when a new version is released. It would be nice to be able to receive such kind of notifications, using email and/or integrations, when the internal LM 'variable' for Settings->Collectors->Updates->Upcoming->version is changing. An addition to that would be some kind of button/link in the notification to process the update for all or some (selected) LM Collectors.