From: Rob R. <rre...@he...> - 2016-07-26 19:55:20
|
Actually, I got it working now. Newbie mistake. In the part of the string that ended with opennms, I didnt realize that was a database name. Changing that to a valid db name on my target node got it working and to my surprise it was smart enough to figure out there were actually three db's in that instance and is collecting on all of them. Thanks, Rob Rob Reinhardt Vice President, Operations Healytics, Inc. On Tue, Jul 26, 2016 at 1:27 PM, Rob Reinhardt <rre...@he...> wrote: > Thanks, I've given it a try. It comes back with the following error at > the RTC for that node. > > PSQL3 data collection on interface a.b.c.d failed with 'An undeclared > throwable was caught during data collection for interface 1/a.b.c.d/PSQL3'. > > One difference I did was instead of just renaming the built-in default > one, I copied and created a new package and gave the new service the PSQL3 > name. I don't know if that is the cause of the problem or not. > > The PSQL3 tcp detector/poller is still working and monitoring, just this > new change didn't work. > > The postgres login and password is correct, I checked it manually. > > I'm not a DBA and I don't know what commands JDBC would be doing that > might be causing errors in order to test them as well. > > Any ideas? > > Rob Reinhardt > Vice President, Operations > Healytics, Inc. > > On Tue, Jul 26, 2016 at 12:12 PM, Aaron Scamehorn-2 [via OpenNMS] <[hidden > email] <http:///user/SendEmail.jtp?type=node&node=7594029&i=0>> wrote: > >> It will perform JDBC queries to collect performance metrics. >> >> On Jul 25, 2016, at 1:11 PM, Rob Reinhardt <[hidden email] >> <http:///user/SendEmail.jtp?type=node&node=7594024&i=0>> wrote: >> >> So, what is that allow it to do? Perform a TCP port check AND JDBC stats >> collection on the same service? >> >> Rob Reinhardt >> Vice President, Operations >> Healytics, Inc. >> >> On Mon, Jul 25, 2016 at 12:51 PM, Aaron Scamehorn-2 [via OpenNMS] <<a >> href="x-msg://55/user/SendEmail.jtp?type=node&node=7594015&i=0" >> target="_top" rel="nofollow" link="external" class="">[hidden email]> >> wrote: >> >>> I renamed the collector service & detector name in >>> collectd-configuration.xml to Postgres. >>> <service name="Postgres" interval="300000" user-defined="false" >>> status="on"> >>> <collector service="Postgres" >>> class-name="org.opennms.netmgt.collectd.JdbcCollector”/> >>> >>> I also added the detector to default-foreign-source.xml: >>> <detector name="Postgres" >>> class="org.opennms.netmgt.provision.detector.simple.TcpDetector”> >>> >>> >>> On Jul 23, 2016, at 2:53 PM, Ronald Roskens <[hidden email] >>> <http://user/SendEmail.jtp?type=node&node=7594014&i=0>> wrote: >>> >>> PostgreSQL is an odd one. >>> >>> Provision Detector: no default detector >>> poller-configuration.xml: service name=“Postgres” >>> collectd-configuration.xml: service name=“PostgreSQL" >>> >>> Back before capsd was removed, there was a TCP detector for the Postgres >>> service. I don’t think that all entries were added to the >>> default-foreign-source.xml. >>> >>> Do we add Postgres detector and rename the entry in >>> collectd-configuration.xml? >>> Do we add a PostgreSQL detector and rename the entry in >>> poller-configuration.xml? >>> What should happen during an upgrade? >>> >>> >>> To explicitly include (or exclude) a polling package for an ip address >>> (because services exist on the ip address, not the node), you need to add >>> one of 5 elements to the package: >>> >>> <filter> >>> <specific> >>> <include-range> >>> <exclude-range> >>> <include-url> >>> >>> Filter uses the same query language as used by notifications. You can >>> use the notification wizard to get an idea of which ip addresses would >>> match against the filter you are writing. You can have only one on a >>> package. >>> >>> There are no limits to the number of specific, include-range, >>> exclude-range, and include-urls you can add to a package. >>> >>> From $OPENNMS_HOME/etc/examples/poller-configuration.xml: >>> >>> ==== >>> <package name="example1"> >>> <filter>IPADDR != '0.0.0.0'</filter> >>> <specific>0.0.0.0</specific> >>> <include-range begin="1.1.1.1" end="254.254.254.254" /> >>> <include-url>file:${install.etc.dir}/include</include-url> >>> ==== >>> >>> Exclude-range is done the same way as include-range, with a begin and >>> end attributes. >>> >>> >>> Ron >>> >>> On Jul 22, 2016, at 1:40 PM, Rob Reinhardt <[hidden email] >>> <http://user/SendEmail.jtp?type=node&node=7594014&i=1>> wrote: >>> >>> Where on the node page UI? >>> >>> I get the nodes name, database ID, requisition, and foreign ID. I see >>> nothing there that talks about polling package. >>> >>> But, more than seeing what polling package a node is in (which would be >>> nice), I really need to know where in the configuration do I *tell* the >>> system *which* polling package to use when its polling? >>> >>> OpenNMS comes with the following packages pre-defined in >>> poller-configuration.xml: >>> >>> <package name="cassandra21x"> >>> <package name="cassandra21x-newts"> >>> <package name="example1"> >>> <package name="strafer"> >>> >>> None of the list of services from any of them exactly match what OpenNMS >>> seems to be "polling by default" in its"default" requisition. So, are any >>> of these actually defining the behavior of my system? >>> >>> After configuring my IP range for discovery it went out and found all >>> ~50 of my nodes by interface and automatically discovered and started >>> monitoring some services. >>> >>> But, there are other services on my nodes that aren't being discovered >>> and monitored. >>> >>> The only built-in polling package that seems comprehensive enough to be >>> defining services for my current polling result is example1. >>> >>> But there are other services in example1 that don't show up in the list >>> of available services when I click in the UI to "edit detectors and >>> policies of the default requisition" and for which I do have services >>> running. >>> >>> An example would be "service name="Postgres" >>> >>> The default neither detects or monitors them. But it is defined in >>> pollers-configuration.xml, yet doesn't show up on the list of available >>> services. >>> >>> Which has indicated to me that example1 isn't controlling what service >>> definitions I have in my poller either. >>> >>> So, then I am stuck with, what is controlling this behavior if not the >>> config in that file? >>> >>> I have gone so far already as created my own package and listed in both >>> sections of the poller-configuration.xml as directed. Also as directed, I >>> added the custom poller as a detector in the default requisition. >>> >>> I have also tried it with and without a custom policy there as well, but >>> the options are limited, the only class to event fit the context of a >>> generic TCP monitor is the first choice >>> "org.opennms.netmgt.provision.persist.policies.MatchingIpInterfacePolicy", >>> and Action "ENABLE_COLLECTION" and matchBehaviour "ANY_PARAMETER." {But >>> there were no other policies defined there for any of the other detectors >>> that are working by default so its not clear this is even the correct thing >>> to do.} >>> >>> I've tried Marcel's example nearly verbatim (just not strafeping but my >>> tcp/5433 real case), and still nothing. >>> >>> --- >>> >>> All of that is troubleshooting really just to try to figure out how this >>> is supposed to be done because doing what the directions say isn't >>> working. I am on version 1.8 (supposedly the most recent stable release) >>> if that makes any difference. >>> >>> I'll tell you the bottom line problem I'm having is that I want/need to >>> define certain custom monitors (services and polling), this postgres >>> example being the simplest. But, for discussion sake, say I simply want to >>> monitor any service on a port that responds to a telnet (like the book >>> example gives, which does work at the cli). >>> >>> I just can't get the RTC to agree with me that I've configured any or >>> that it should monitor it. >>> >>> I got the RTC to detect the service (so something must've been done >>> correctly) but it just continues to say "Not Monitored" no matter how many >>> different ways I try to get this configuration into the poller. >>> >>> If anyone has a handy quick-reference guide of precise steps and good >>> examples to follow to do this, I'd appreciate a copy. So far nothing I >>> have found in http://docs.opennms.org or http://wiki.opennms.org has >>> anything I haven't already tried and re-tried and tweaked. >>> >>> Thanks, >>> Rob >>> >>> >>> >>> >>> >>> >>> >>> Rob Reinhardt >>> Vice President, Operations >>> Healytics, Inc. >>> >>> On Thu, Jul 21, 2016 at 12:49 PM, David S Hustace [via OpenNMS] <<a >>> href="<a >>> href="x-msg://23/user/SendEmail.jtp?type=node&amp;node=7594008&amp;i=0" >>> class="">x-msg://23/user/SendEmail.jtp?type=node&node=7594008&i=0" >>> target="_top" rel="nofollow" link="external" class="">[hidden email]> >>> wrote: >>> >>>> >>>> > On Jul 21, 2016, at 10:44 AM, Fuhrmann, Marcel <[hidden email] >>>> <http://user/SendEmail.jtp?type=node&node=7594006&i=0>> wrote: >>>> > >>>> > How do you tell OpenNMS which poller package to use / to run? >>>> >>>> You can see this in the UI on the node page. >>>> >>>> >>>> :David Hustace >>>> >>>> David Hustace >>>> The OpenNMS Group, Inc. >>>> >>>> ------------------------------------------------------------------------------ >>>> >>>> What NetFlow Analyzer can do for you? Monitors network bandwidth and >>>> traffic >>>> patterns at an interface-level. Reveals which users, apps, and >>>> protocols are >>>> consuming the most bandwidth. Provides multi-vendor support for >>>> NetFlow, >>>> J-Flow, sFlow and other flows. Make informed decisions using capacity >>>> planning >>>> reports.http://sdm.link/zohodev2dev >>>> _______________________________________________ >>>> Please read the OpenNMS Mailing List FAQ: >>>> http://www.opennms.org/index.php/Mailing_List_FAQ >>>> >>>> opennms-discuss mailing list >>>> >>>> To *unsubscribe* or change your subscription options, see the bottom of >>>> this page: >>>> https://lists.sourceforge.net/lists/listinfo/opennms-discuss >>>> >>>> *signature.asc* (858 bytes) Download Attachment >>>> <http://opennms.530661.n2.nabble.com/attachment/7594006/0/signature.asc> >>>> >>>> >>>> ------------------------------ >>>> If you reply to this email, your message will be added to the >>>> discussion below: >>>> >>>> http://opennms.530661.n2.nabble.com/poller-package-question-tp7594002p7594006.html >>>> To unsubscribe from poller package question, click here. >>>> NAML >>>> <http://opennms.530661.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> >>>> >>> >>> >>> ------------------------------ >>> View this message in context: Re: poller package question >>> <http://opennms.530661.n2.nabble.com/poller-package-question-tp7594002p7594008.html> >>> Sent from the OpenNMS - discuss mailing list archive >>> <http://opennms.530661.n2.nabble.com/OpenNMS-discuss-f529575.html> at >>> Nabble.com <http://nabble.com/>. >>> >>> ------------------------------------------------------------------------------ >>> What NetFlow Analyzer can do for you? Monitors network bandwidth and >>> traffic >>> patterns at an interface-level. Reveals which users, apps, and protocols >>> are >>> consuming the most bandwidth. Provides multi-vendor support for NetFlow, >>> J-Flow, sFlow and other flows. Make informed decisions using capacity >>> planning >>> reports. >>> http://sdm.link/zohodev2dev_______________________________________________ >>> Please read the OpenNMS Mailing List FAQ: >>> http://www.opennms.org/index.php/Mailing_List_FAQ >>> >>> opennms-discuss mailing list >>> >>> To *unsubscribe* or change your subscription options, see the bottom of >>> this page: >>> https://lists.sourceforge.net/lists/listinfo/opennms-discuss >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> What NetFlow Analyzer can do for you? Monitors network bandwidth and >>> traffic >>> patterns at an interface-level. Reveals which users, apps, and protocols >>> are >>> consuming the most bandwidth. Provides multi-vendor support for NetFlow, >>> J-Flow, sFlow and other flows. Make informed decisions using capacity >>> planning >>> reports. >>> http://sdm.link/zohodev2dev_______________________________________________ >>> Please read the OpenNMS Mailing List FAQ: >>> http://www.opennms.org/index.php/Mailing_List_FAQ >>> >>> opennms-discuss mailing list >>> >>> To *unsubscribe* or change your subscription options, see the bottom of >>> this page: >>> https://lists.sourceforge.net/lists/listinfo/opennms-discuss >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> What NetFlow Analyzer can do for you? Monitors network bandwidth and >>> traffic >>> patterns at an interface-level. Reveals which users, apps, and protocols >>> are >>> consuming the most bandwidth. Provides multi-vendor support for NetFlow, >>> J-Flow, sFlow and other flows. Make informed decisions using capacity >>> planning >>> reports.http://sdm.link/zohodev2dev >>> _______________________________________________ >>> Please read the OpenNMS Mailing List FAQ: >>> http://www.opennms.org/index.php/Mailing_List_FAQ >>> >>> opennms-discuss mailing list >>> >>> To *unsubscribe* or change your subscription options, see the bottom of >>> this page: >>> https://lists.sourceforge.net/lists/listinfo/opennms-discuss >>> >>> ------------------------------ >>> If you reply to this email, your message will be added to the discussion >>> below: >>> >>> http://opennms.530661.n2.nabble.com/poller-package-question-tp7594002p7594014.html >>> To unsubscribe from poller package question, click here. >>> NAML >>> <http://opennms.530661.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> >>> >> >> >> ------------------------------ >> View this message in context: Re: poller package question >> <http://opennms.530661.n2.nabble.com/poller-package-question-tp7594002p7594015.html> >> Sent from the OpenNMS - discuss mailing list archive >> <http://opennms.530661.n2.nabble.com/OpenNMS-discuss-f529575.html> at >> Nabble.com <http://nabble.com>. >> >> ------------------------------------------------------------------------------ >> What NetFlow Analyzer can do for you? Monitors network bandwidth and >> traffic >> patterns at an interface-level. Reveals which users, apps, and protocols >> are >> consuming the most bandwidth. Provides multi-vendor support for NetFlow, >> J-Flow, sFlow and other flows. Make informed decisions using capacity >> planning >> reports. >> http://sdm.link/zohodev2dev_______________________________________________ >> Please read the OpenNMS Mailing List FAQ: >> http://www.opennms.org/index.php/Mailing_List_FAQ >> >> opennms-discuss mailing list >> >> To *unsubscribe* or change your subscription options, see the bottom of >> this page: >> https://lists.sourceforge.net/lists/listinfo/opennms-discuss >> >> >> >> ------------------------------------------------------------------------------ >> >> What NetFlow Analyzer can do for you? Monitors network bandwidth and >> traffic >> patterns at an interface-level. Reveals which users, apps, and protocols >> are >> consuming the most bandwidth. Provides multi-vendor support for NetFlow, >> J-Flow, sFlow and other flows. Make informed decisions using capacity >> planning >> reports.http://sdm.link/zohodev2dev >> _______________________________________________ >> Please read the OpenNMS Mailing List FAQ: >> http://www.opennms.org/index.php/Mailing_List_FAQ >> >> opennms-discuss mailing list >> >> To *unsubscribe* or change your subscription options, see the bottom of >> this page: >> https://lists.sourceforge.net/lists/listinfo/opennms-discuss >> >> ------------------------------ >> If you reply to this email, your message will be added to the discussion >> below: >> >> http://opennms.530661.n2.nabble.com/poller-package-question-tp7594002p7594024.html >> To unsubscribe from poller package question, click here. >> NAML >> <http://opennms.530661.n2.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> >> > > > ------------------------------ > View this message in context: Re: poller package question > <http://opennms.530661.n2.nabble.com/poller-package-question-tp7594002p7594029.html> > Sent from the OpenNMS - discuss mailing list archive > <http://opennms.530661.n2.nabble.com/OpenNMS-discuss-f529575.html> at > Nabble.com. > > > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > patterns at an interface-level. Reveals which users, apps, and protocols > are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning > reports.http://sdm.link/zohodev2dev > _______________________________________________ > Please read the OpenNMS Mailing List FAQ: > http://www.opennms.org/index.php/Mailing_List_FAQ > > opennms-discuss mailing list > > To *unsubscribe* or change your subscription options, see the bottom of > this page: > https://lists.sourceforge.net/lists/listinfo/opennms-discuss > |