This list is closed, nobody may subscribe to it.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(35) |
Oct
(15) |
Nov
(68) |
Dec
(35) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(146) |
Feb
(175) |
Mar
(194) |
Apr
(170) |
May
(159) |
Jun
(190) |
Jul
(166) |
Aug
(79) |
Sep
(115) |
Oct
(104) |
Nov
(205) |
Dec
(209) |
2002 |
Jan
(147) |
Feb
(184) |
Mar
(314) |
Apr
(623) |
May
(387) |
Jun
(242) |
Jul
(311) |
Aug
(352) |
Sep
(278) |
Oct
(277) |
Nov
(329) |
Dec
(287) |
2003 |
Jan
(563) |
Feb
(401) |
Mar
(371) |
Apr
(402) |
May
(304) |
Jun
(268) |
Jul
(402) |
Aug
(253) |
Sep
(428) |
Oct
(334) |
Nov
(225) |
Dec
(360) |
2004 |
Jan
(282) |
Feb
(431) |
Mar
(441) |
Apr
(230) |
May
(244) |
Jun
(264) |
Jul
(279) |
Aug
(361) |
Sep
(371) |
Oct
(301) |
Nov
(291) |
Dec
(239) |
2005 |
Jan
(240) |
Feb
(411) |
Mar
(343) |
Apr
(254) |
May
(195) |
Jun
(343) |
Jul
(298) |
Aug
(361) |
Sep
(424) |
Oct
(376) |
Nov
(259) |
Dec
(234) |
2006 |
Jan
(272) |
Feb
(348) |
Mar
(543) |
Apr
(465) |
May
(219) |
Jun
(306) |
Jul
(243) |
Aug
(272) |
Sep
(321) |
Oct
(420) |
Nov
(368) |
Dec
(219) |
2007 |
Jan
(511) |
Feb
(328) |
Mar
(418) |
Apr
(500) |
May
(441) |
Jun
(552) |
Jul
(481) |
Aug
(452) |
Sep
(443) |
Oct
(435) |
Nov
(489) |
Dec
(449) |
2008 |
Jan
(777) |
Feb
(684) |
Mar
(785) |
Apr
(638) |
May
(616) |
Jun
(580) |
Jul
(705) |
Aug
(402) |
Sep
(624) |
Oct
(719) |
Nov
(556) |
Dec
(438) |
2009 |
Jan
(365) |
Feb
(343) |
Mar
(561) |
Apr
(499) |
May
(412) |
Jun
(360) |
Jul
(383) |
Aug
(486) |
Sep
(602) |
Oct
(518) |
Nov
(673) |
Dec
(360) |
2010 |
Jan
(423) |
Feb
(467) |
Mar
(510) |
Apr
(516) |
May
(393) |
Jun
(585) |
Jul
(635) |
Aug
(447) |
Sep
(671) |
Oct
(434) |
Nov
(385) |
Dec
(369) |
2011 |
Jan
(317) |
Feb
(377) |
Mar
(401) |
Apr
(304) |
May
(323) |
Jun
(270) |
Jul
(304) |
Aug
(180) |
Sep
(177) |
Oct
(252) |
Nov
(235) |
Dec
(261) |
2012 |
Jan
(268) |
Feb
(298) |
Mar
(287) |
Apr
(240) |
May
(242) |
Jun
(290) |
Jul
(437) |
Aug
(305) |
Sep
(216) |
Oct
(223) |
Nov
(302) |
Dec
(194) |
2013 |
Jan
(289) |
Feb
(224) |
Mar
(287) |
Apr
(230) |
May
(279) |
Jun
(201) |
Jul
(323) |
Aug
(276) |
Sep
(274) |
Oct
(160) |
Nov
(239) |
Dec
(152) |
2014 |
Jan
(225) |
Feb
(174) |
Mar
(242) |
Apr
(112) |
May
(102) |
Jun
(184) |
Jul
(96) |
Aug
(90) |
Sep
(118) |
Oct
(171) |
Nov
(212) |
Dec
(123) |
2015 |
Jan
(130) |
Feb
(161) |
Mar
(152) |
Apr
(105) |
May
(147) |
Jun
(152) |
Jul
(136) |
Aug
(125) |
Sep
(99) |
Oct
(92) |
Nov
(133) |
Dec
(169) |
2016 |
Jan
(131) |
Feb
(89) |
Mar
(138) |
Apr
(71) |
May
(73) |
Jun
(80) |
Jul
(122) |
Aug
(89) |
Sep
(126) |
Oct
(136) |
Nov
(120) |
Dec
(96) |
2017 |
Jan
(107) |
Feb
(171) |
Mar
(301) |
Apr
(164) |
May
(161) |
Jun
(84) |
Jul
(113) |
Aug
(61) |
Sep
(56) |
Oct
(75) |
Nov
(57) |
Dec
(27) |
2018 |
Jan
(34) |
Feb
(46) |
Mar
(44) |
Apr
(31) |
May
(56) |
Jun
(47) |
Jul
(71) |
Aug
(74) |
Sep
(44) |
Oct
(57) |
Nov
(36) |
Dec
(46) |
2019 |
Jan
(22) |
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: GOPI G. <gop...@gm...> - 2019-02-14 07:18:04
|
Hi, I had installed OPENNMS in my windows server 2012. And while opening URL in browser it is showing error connection refused. I had run the command in CMD prompt netstat -a In that, I am unable to see port 8980. Can you please help on this. Regards Grandhi Gopi. |
From: Benjamin R. <ra...@op...> - 2019-02-11 19:56:59
|
It's time for This Week in OpenNMS! Last week we added a ton of extensions to the OpenNMS Integration API, did more wrap-up on various modernization and refactoring projects, and fixed more bugs. *This is the last week you can get TWiO in e-mail from these mailing lists. In the future you can either subscribe to the the **RSS <https://www.opennms.orghttps://www.opennms.org/en/blog/twio.rss>**or **Atom <https://www.opennms.orghttps://www.opennms.org/en/blog/twio.atom>**feeds, or read it on **our Discourse <https://opennms.discourse.group/c/announcements/twio>**.* <#github-project-updates>Github Project Updates * *Internals, APIs, and Documentation* o Jesse did some work on refactoring poller configuration handling. o Jesse added node assets, event handling, and graphs to the OIA. o Markus did more work on the new core graph API and ReST service. o David and Matt worked on a number of changes to our maven build to facilitate Java 9+ support. o Christian worked on wrapping up his DHCP monitor and detector refactor. o Jeff fixed a configuration consistency issue in the Slack notification strategy. o Chandra worked on collector support in the OIA. o Jesse made some enhancements to the requisition support in OIA. o Dustin has been working on adding support for arbitrary node metadata in requisitions. o I added test coverage and fixed a few bugs in the |opennms| and |runjava| CLI scripts. o Jesse did some wrap-up on Elasticsearch alarm indexing support. o Jesse added support for configuring connection pooling options for Newts. o Ronny added some documentation for SNMP trap reception in Minion. o Patrick added support for unit testing topology providers using the refactored topology generator API. o Chandra improved collection-handling to log exceptions in a useful manner. o Chandra fixed health check to only check ActiveMQ connectivity if it's enabled for sink/RPC. * *Web & UI* o Matt did some fixes to some header defaults in Jetty. o Matt fixed some bugs in locale handling in the web UI. o Dustin fixed Helm so it the order of responses always matches the query. o Markus did some refactoring of the daemon reload web UI work. o I added linting to the Helm codebase and cleaned up some warnings. o Dustin finished up his work on browser notification support. o Markus did some more tweaks to the Bootstrap 4 UI refactor based on feedback. <#upcoming-events-and-appearances>Upcoming Events and Appearances * *NETHINKS Training in Fulda, Germany - June and October <https://www.nethinks.com/opennms-schulung.html>* NETHINKS will be offering German-language training in their headquarters in Fulda, Germany. There are 2 dates available: o June 3rd through 7th o October 21st through 25th For more details or to sign up, see the NETHINKS training page <https://www.nethinks.com/opennms-schulung.html>. * *OSMC 2019 in Nuremberg, Germany - November 4th through 7th <https://osmc.de/>* We will be at OSMC in November. Details are still forthcoming but we're hoping to do a 1-day workshop. For more information on OSMC, see their website <https://osmc.de/>. <#until-next-week>Until Next Week… If there’s anything you’d like me to talk about in a future TWiO, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi <mailto:tw...@op...>. - Ben <#resolved-issues-since-last-twio>Resolved Issues Since Last TWiO * HELM-128 <https://issues.opennms.org/browse/HELM-128>: Measurements API does not preserve series order * HELM-129 <https://issues.opennms.org/browse/HELM-129>: Allow queries with missing attributes * HZN-956 <https://issues.opennms.org/browse/HZN-956>: Support Browser Notification API * HZN-1198 <https://issues.opennms.org/browse/HZN-1198>: CDP Topology not discovered on Cisco Nexus devices * HZN-1231 <https://issues.opennms.org/browse/HZN-1231>: Upgrade the maven-war-plugin * HZN-1420 <https://issues.opennms.org/browse/HZN-1420>: Index alarms and alarm history in Elasticsearch * HZN-1471 <https://issues.opennms.org/browse/HZN-1471>: Provide capability to expose GraphContainerProviders with only one graph (SingleGraphContainerProvider) * HZN-1472 <https://issues.opennms.org/browse/HZN-1472>: Make GraphRepository accessible via OSGI * NMS-8185 <https://issues.opennms.org/browse/NMS-8185>: Create a reload daemon configuration page * NMS-10486 <https://issues.opennms.org/browse/NMS-10486>: syslog events are creating notifications and disregarding rules in place * NMS-10496 <https://issues.opennms.org/browse/NMS-10496>: Update flow classification rules to match either the src or dst ports * NMS-10546 <https://issues.opennms.org/browse/NMS-10546>: Cross-Site Scripting: Reflected * NMS-10547 <https://issues.opennms.org/browse/NMS-10547>: Cross-Frame Scripting * NMS-10557 <https://issues.opennms.org/browse/NMS-10557>: Upgrade liquibase to 3.x * OCE-38 <https://issues.opennms.org/browse/OCE-38>: Add log rotation support to the kafka-event-mirrorer |
From: Dustin F. <fo...@la...> - 2019-02-06 22:41:00
|
[English text below] Liebe Mitglieder, gerne möchten wir Euch zu einer ordentlichen Mitgliederversammlung der OpenNMS Foundation Europe e.V. einladen: Donnerstag, 21. Februar 18:00 bis 20:00 CET Bahnhofstraße 16, 36037 Fulda Agenda: * Bericht des Vorstands * Finanzbericht 2017 * Auflösung des Vereins * Wahl des Vorstandes * Allgemeines Wir werden kurzfrisitg vor der Mitgliederversammlung eine Möglichkeit zur Fernmündlichen Teilnahme bekanntgeben. Mit freundlichen Grüßen Dustin Frisch -------- Dear Members we kindly invite you to a general assembly of the OpenNMS Foundation Europe e.V.: Thursday, 21. Februar 18:00 to 20:00 CET Bahnhofstraße 16, 36037 Fulda, Germany Agenda: * Information from the board * Financial report 2017 * Dissolution of the Foundation * Election of a new board * Divers We will provide a way for remote participation right before the meeting starts. Best Regards Dustin Frisch |
From: Benjamin R. <ra...@op...> - 2019-02-04 17:23:26
|
It's time for This Week in OpenNMS! Last week we did more bugfix, infrastructure, and Java 9+ updating, plus we started wrapping up the UI refresh and some other projects. <#github-project-updates>Github Project Updates * *Internals, APIs, and Documentation* o Antonio continued his work exposing topology data to Kafka. o Ronny has been working on an official workflow for publishing OpenNMS/Minion/Sentinel Docker containers from CI. o I did more work on moving to Liquibase 3 for database schema management. o Markus continued to develop a new graph service/API. o Dustin wrapped up changing flow support to index by application rather than by port. o Jesse updated our test infrastructure to use Elasticsearch 6.5. o Christian did more work on modernizing our DHCP handling. o Chandra continued to develop a fix for handling notifications without associated nodes. o Jesse fixed a performance issue when loading a large number of nodes. o Patrick continued his work exposing the topology creator to the Karaf CLI. o David worked on updating some build infrastructure to work with Java 9+. o I fixed an issue with syslog parsing that could cause the wrong year to be used in some cases. o Jesse worked on requisition providers in OIA. o Jesse did some performance improvements on the Alarmd Drools context handling. * *Web & UI* o Markus continued to do minor tweaks to the Bootstrap 4 UI rework, readying it for merging. o Jesse updated Helm to support the measurements API "relaxed" mode, allowing for queries to reference missing series. o Christian fixed the SNMP config page to select the "Default" location by default. o Sebastian fixed an issue with form validation in the notification editor. o Markus made some more changes to the daemon reload page. <#opennms-mailing-lists-going-away>OpenNMS Mailing Lists Going Away We had originally planned on decommissioning the mailing lists in August. However, based on the feedback we got, it seemed that people wanted something additional between Stack Overflow and real-time chat suggested in the original announcement. Since then, we have set up a Discourse that should give the ability to do most of what was done on the mailing lists, including getting email notifications of discussion threads you're interested in. So with that in mind, here's what you need to know: <#list-shutdown--archives>List Shutdown & Archives All OpenNMS mailing lists will be shut down on Friday, February 15th. If you wish to read historical messages, they are archived on marc.info: * https://marc.info/?l=opennms-announce * https://marc.info/?l=opennms-discuss * https://marc.info/?l=opennms-install ...and so on. <#real-time-chat>Real-Time Chat If you wish to talk to OpenNMS developers and users, you can access our chat server at: https://chat.opennms.com/ For old-skoolers, you can also connect through IRC, once you have created a user account on chat.opennms.com <https://chat.opennms.com/>. To do so, connect to |chat.opennms.com| (port |6667|) with your IRC client, and then do: |/msg mattermost login chat.opennms.com opennms <email> <password>| <#discourse-forums>Discourse Forums To access the OpenNMS Discourse, just go to: https://opennms.discourse.group/ It works like most forum sites. If you wish it to behave a bit more like the old mailing lists, you can go to your preferences and enable "Mailing List Mode" which will send you an email whenever new topics are created. <#configuration-questions>Configuration Questions There is technically an |opennms| tag on Stack Overflow, but Stack Overflow is really for development questions, not configuration questions. Instead of posting to Stack Overflow, please use the /"Community Support"/ section of the Discourse: https://opennms.discourse.group/c/community-support <#until-next-week>Until Next Week… If there’s anything you’d like me to talk about in a future TWiO, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi <mailto:tw...@op...>. - Ben <#resolved-issues-since-last-twio>Resolved Issues Since Last TWiO * HZN-1232 <https://issues.opennms.org/browse/HZN-1232>: Update GWT to >= 2.8.2 * HZN-1443 <https://issues.opennms.org/browse/HZN-1443>: Update the elasticsearch-drift-plugin to support Elasticsearch v6.5.x * HZN-1449 <https://issues.opennms.org/browse/HZN-1449>: Improve performance of DroolsAlarmContext alarm snapshot handling * HZN-1464 <https://issues.opennms.org/browse/HZN-1464>: Core structure/API of new Graph Service * HZN-1466 <https://issues.opennms.org/browse/HZN-1466>: Upgrade to Jetty 9.4.12 * HZN-1467 <https://issues.opennms.org/browse/HZN-1467>: Upgrade Elasticsearch test server to use v6.5.x * NMS-10411 <https://issues.opennms.org/browse/NMS-10411>: Create documentation for the reloadable flag in service-configuration.xml * NMS-10497 <https://issues.opennms.org/browse/NMS-10497>: Track (flow) conversations by application instead of src/dst port * NMS-10506 <https://issues.opennms.org/browse/NMS-10506>: Node page very slow to load for nodes with more than 1000 events * NMS-10514 <https://issues.opennms.org/browse/NMS-10514>: SNMP configuration UI should select location "Default" by default, not the first location alphabetically * NMS-10533 <https://issues.opennms.org/browse/NMS-10533>: Make Topology Creator as Karaf command available * NMS-10541 <https://issues.opennms.org/browse/NMS-10541>: Recent Debian builds can't be installed on Ubuntu 14 * NMS-10548 <https://issues.opennms.org/browse/NMS-10548>: syslog parsing of messages without a year will sometimes infer the wrong year * OCE-37 <https://issues.opennms.org/browse/OCE-37>: Build a map from two different OCE Datasets |
From: Chuck h. <cha...@ch...> - 2019-01-31 21:40:11
|
Hi I have version 22.0.3 of Horizon. this is a new install and I am having problems receiving events via eMail (google email). I had this working on an older version of horizon. but now I can't seem to get this working my new install. I am not sure where it is failing. I am wondering if someone cant point me to see where this is failing... thanks Here is what I have done. I have set notices to on All event notifications in "/admin/Configuration Notifications/Event Notifications" are enabled I have configured "Configure Destination Paths" to send email to my gmail account Here is my "javamail-configuration.properties file ############################################################################## # This file is the configuration for the the JavaMailer class. It is used to # specify the details of the JavaMailer system properties ################################################################################ # # Properties are defined but commented out indicating the default values. # # # This property defines system sender account. # # The default setting is root@[127.0.0.1] #org.opennms.core.utils.fromAddress=root@[127.0.0.1] org.opennms.core.utils.fromAddress=admin@talgor.host.local # # These properties define the SMTP Host. # org.opennms.core.utils.mailHost=127.0.0.1 #org.opennms.core.utils.mailer=smtpsend #org.opennms.core.utils.transport=smtp #org.opennms.core.utils.debug=true org.opennms.core.utils.smtpport=25 #org.opennms.core.utils.smtpssl.enable=false #org.opennms.core.utils.quitwait=true # # This property controls the use of the JMTA # if it is true, mailHost will be ignored org.opennms.core.utils.useJMTA=false # # These properties define the Mail authentication. # #org.opennms.core.utils.authenticate=false #org.opennms.core.utils.authenticateUser=opennms #org.opennms.core.utils.authenticatePassword=opennms #org.opennms.core.utils.starttls.enable=false # # These properties configure message content # #org.opennms.core.utils.messageContentType=text/plain org.opennms.core.utils.transport=smtps org.opennms.core.utils.mailHost=smtp.gmail.com org.opennms.core.utils.smtpport=465 org.opennms.core.utils.smtpssl.enable=true org.opennms.core.utils.authenticate=true org.opennms.core.utils.authenticateUser=us...@gm... org.opennms.core.utils.authenticatePassword=###### org.opennms.core.utils.starttls.enable=false org.opennms.core.utils.messageContentType=text/html org.opennms.core.utils.charset=UTF-8 #org.opennms.core.utils.charset=us-ascii *Notice of Confidentiality:* *This transmission constitutes an electronic communication within the meaning of the Electronic Commissions Privacy Act, 18 U.S.C. 2510, and its disclosure is strictly limited to the recipient intended by the sender of this message, together with any attachments. This communication, including any attachments, may contain confidential and privileged material for the sole use of the intended individual or entity, and receipt by any party other than the intended recipient does not constitute a loss of the confidential or privileged nature of the communication. * *Any review or distribution by others is prohibited:* *If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately by telephone or by return E-mail and delete this message, along with any attachments, from your computer.* . Thank you kindly chuck harpham _____ |__/__| (0||||0) Sit vis vobiscum [image: linkedin icon] linkedin.com/in/charpham411 |
From: Benjamin R. <ra...@op...> - 2019-01-31 18:55:22
|
We had originally planned on decommissioning the mailing lists in August. However, based on the feedback we got, it seemed that people wanted something additional between Stack Overflow and real-time chat suggested in the original announcement. Since then, we have set up a Discourse that should give the ability to do most of what was done on the mailing lists, including getting email notifications of discussion threads you're interested in. So with that in mind, here's what you need to know: List Shutdown & Archives ======================== All OpenNMS mailing lists will be shut down on Friday, February 15th. If you wish to read historical messages, they are archived on marc.info: https://marc.info/?l=opennms-announce https://marc.info/?l=opennms-discuss https://marc.info/?l=opennms-install ...and so on. Real-Time Chat ============== If you wish to talk to OpenNMS developers and users, you can access our chat server at: https://chat.opennms.com/ For old-skoolers, you can also connect through IRC, once you have created a user account on chat.opennms.com. To do so, connect to chat.opennms.com (port 6667) with your IRC client, and then do: /msg mattermost login chat.opennms.com opennms <email> <password> Discourse Forums ================ To access the OpenNMS Discourse, just go to: https://opennms.discourse.group/ It works like most forum sites. If you wish it to behave a bit more like the old mailing lists, you can go to your preferences and enable "Mailing List Mode" which will send you an email whenever new topics are created. Configuration Questions ======================= There is technically an `opennms` tag on Stack Overflow, but Stack Overflow is really for development questions, not configuration questions. Instead of posting to Stack Overflow, please use the "Community Support" section of the Discourse: https://opennms.discourse.group/c/community-support That's It ========= If you have any questions, please let me know. |
From: Benjamin R. <ra...@op...> - 2019-01-28 19:41:33
|
It's time for This Week in OpenNMS! Last week we continued a lot of existing projects as well as more bugfixes. <#github-project-updates>Github Project Updates * *Internals, APIs, and Documentation* o Antonio continued his work exposing topology data to Kafka. o Patrick worked on porting/refactoring the tool to generate test topologies to the Karaf CLI. o Markus did more work on a new graph service API. o I worked on updating our embedded Karaf to 4.2.2. o Patrick did more work on his SNMP collector refactor/replacement. o Chandra worked on an issue with notifications being sent with no associated nodes. o Jesse continued to tune his updates to Elasticsearch support. o Jesse refactored the event configuration Karaf shell tool to rely only on the OIA. o I worked on updating us to the latest PostgreSQL JDBC driver. * *Web & UI* o Sebastian did some more work on the daemon refactor and reload page. o Markus, Sebastian, and Ronny continued their work on moving to Bootstrap 4 for our web UI. o I worked on updating us to the latest version of Jetty 9. <#upcoming-events-and-appearances>Upcoming Events and Appearances * *FOSDEM - Brussels, Belgium - February 2nd and 3rd, 2019 <https://fosdem.org/2019/>* Craig Gallen will be giving a lightning talk on OpenNMS and MQTT <https://fosdem.org/2019/schedule/track/lightning_talks/> at FOSDEM in Brussels this year. <#until-next-week>Until Next Week… If there’s anything you’d like me to talk about in a future TWiO, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi <mailto:tw...@op...>. - Ben <#resolved-issues-since-last-twio>Resolved Issues Since Last TWiO * HELM-84 <https://issues.opennms.org/browse/HELM-84>: Display human readable values from nodeResources and nodeFilter * HZN-1442 <https://issues.opennms.org/browse/HZN-1442>: Update the SnmpCollector to use the CollectionSetBuilder * HZN-1461 <https://issues.opennms.org/browse/HZN-1461>: View event configuration definitions from the Karaf shell * NMS-9711 <https://issues.opennms.org/browse/NMS-9711>: Minion WSMAN collector is not functional due to dependency missing * NMS-10477 <https://issues.opennms.org/browse/NMS-10477>: Use a utility function instead of Integer.getInteger * NMS-10505 <https://issues.opennms.org/browse/NMS-10505>: Add karaf logging configuration for Minion/Sentinel * NMS-10515 <https://issues.opennms.org/browse/NMS-10515>: Wallboard URLs with board name should be permalinks, but return "Nothing to display" instead * NMS-10525 <https://issues.opennms.org/browse/NMS-10525>: Event parameters table have strong limits for the columns * OCE-36 <https://issues.opennms.org/browse/OCE-36>: Export data from OpenNMS (stored in ES) to an OCE Dataset |
From: Hernandez, P. <Pau...@me...> - 2019-01-28 17:25:29
|
2nd try. Anyone? Thanks much, Paul From: Hernandez, Paul Sent: Tuesday, January 8, 2019 2:03 PM To: 'General OpenNMS Discussion' <ope...@li...> Subject: CPU util statistics using all possible instance numbers Hello, By referencing this doc: https://wiki.opennms.org/wiki/Enable_monitoring_of_CPU_utilization_on_Windows_systems I was able to set up CPU utilization monitoring in similar fashion on Linux hosts. My question is with regard to the use of Resource Filters and Regular Expressions via the Edit threshold form. The example in the doc above is hard-coded to assume a host has 32 cores and uses a group named “windows-host” with 32 mibObj lines. Is it possible to author a more general case solution since the more common situation is to have hosts with from 2 to 64 cores in one’s compute farm? In other words, the goal above was to define the threshold as exceeded only when all of the cores on the host exceed a given utilization. This is exactly what is desired, but what can I do, if anything. to config opennms to walk over the entire set of instances of hrProcessorLoad available for a given size host, whether it is 2 instances or 64 of them? Thanks! Paul |
From: Benjamin R. <ra...@op...> - 2019-01-22 16:55:40
|
It's time for This Week in OpenNMS! Last week we worked on a number of Kafka-related fixes and improvements, improved minion monitor support, the Bootstrap 4 UI rework, and a bunch of other bug fixes and enhancements. <#github-project-updates>Github Project Updates * *Internals, APIs, and Documentation* o Chandra worked on an issue where syslog events could trigger notifications when they are not supposed to. o Antonio continued his work on exposing topology data to Kafka. o Jesse fixed an issue where some event parameter names would be too long to be persisted to the database. o Chandra did more work on supporting large buffer sizes in Kafka RPC. o Christian worked on modernizing the DHCP monitor to be Minion-capable. o Jesse continued to work on updating pushing data to Elasticsearch. o Chandra did more changes to the poller API support in OIA. o Dino worked on supporting getting provisioning asset information from WS-Man. o Jesse added support for printing runtime event configuration from the Karaf CLI. o Jesse added Helm documentation for the performance datasource. o Jesse fixed some issues in the Minion WS-Man support. o Matt continued to work on tools to help evaluate alarm and situation coverage. * *Web & UI* o Markus, Sebastian, and Ronny continued their work on moving to Bootstrap 4 for our web UI. o Markus fixed an issue with exceptions in OSGi-provided ReST services getting eaten. o Christian worked on an issue where the wallboard UI would show "Nothing to display". o Markus fixed a problem where the Business Service Status panel would not show. o I worked on making it possible to use node or resource labels and names in Helm datasource labels. o Dustin did some refactoring of the code for supporting browser notifications. o Brynjar Eide worked on adding some missing thread pool information from Collectd and Pollerd's instrumentation. o Dustin worked on making Helm's queries to the measurements API have a consistent order. <#opennms-meridian-and-horizon-releases>OpenNMS Meridian and Horizon Releases Last week we released Meridian 2018.1.4 and Horizon 23.0.2. Both were primarily bugfix releases that also included a number of performance improvements to topology map loading. For a complete list of changes, see the release announcements: * Meridian 2018.1.4 <https://www.opennms.com/2019/01/18/opennms-meridian-2018-1-4-released/> * Horizon 23.0.2 <https://www.opennms.org/en/blog/releases/2019-01-17-opennms-horizon-23.0.2> <#until-next-week>Until Next Week… If there’s anything you’d like me to talk about in a future TWiO, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi <mailto:tw...@op...>. - Ben <#resolved-issues-since-last-twio>Resolved Issues Since Last TWiO * HZN-1458 <https://issues.opennms.org/browse/HZN-1458>: No stack-traces for exceptions thrown by REST services in OSGi * HZN-1460 <https://issues.opennms.org/browse/HZN-1460>: Add option to syslogd to include the raw syslog message as a parameter in the generated event * NMS-10357 <https://issues.opennms.org/browse/NMS-10357>: Improve Collectd and Pollerd's ThreadPool graphs * NMS-10404 <https://issues.opennms.org/browse/NMS-10404>: Support provisioning asset information via wsman * NMS-10441 <https://issues.opennms.org/browse/NMS-10441>: Update favicon.ico for higher resolutions * NMS-10446 <https://issues.opennms.org/browse/NMS-10446>: Support large buffer sizes in Kafka RPC * NMS-10449 <https://issues.opennms.org/browse/NMS-10449>: Use the DaemonService to reload a daemon instead of the DaemonNameEnum * NMS-10518 <https://issues.opennms.org/browse/NMS-10518>: refactor/clean up |opennms| script * NMS-10527 <https://issues.opennms.org/browse/NMS-10527>: Remove unused Topology Plugin "org.opennms.features.topology.plugins.ssh" * NMS-10529 <https://issues.opennms.org/browse/NMS-10529>: BusinessServiceVertexStatusInfoPanelItem is broken * NMS-10530 <https://issues.opennms.org/browse/NMS-10530>: Flow query fails with NPE if it returns no data * OIA-1 <https://issues.opennms.org/browse/OIA-1>: Add support for ServiceMonitors |
From: Seibold, M. <mic...@gk...> - 2019-01-18 14:27:24
|
Hi all, does anyone know how to preserver a manual topology map layout during software upgrades? I saved the link as provided from the topology web page, but the icon's are spread all over the screen after the upgrade. We have topology maps with several hundred systems where we put a lot of work into the manual layout. After software updates we have to redo all the work (David, do you remember the times (I won't write "good old times) with Netview? My wristle still aches ...). Thanks Michael |
From: Benjamin R. <ra...@op...> - 2019-01-14 16:59:44
|
It's time for This Week in OpenNMS! Last week we did more alarm correlation updates, lots of Kafka fixes and enhancements, worked on a new SNMP collector, and did a lot of other smaller changes. <#github-project-updates>Github Project Updates * *Internals, APIs, and Documentation* o Jesse worked on handling clock skew when triggering alarms in Alarmd. o Matt worked on making it possible for the integration API to handle situation feedback without Kafka. o Antonio continued his work to publish topology data to Kafka. o Patrick started work on a new SnmpCollector that works with Minions. o Chandra did more work on handling caching/large buffer sizes in Kafka RPC. o I did some more fixes to my |opennms| shell refactor. o I worked on attempting to update to a newer version of HikariCP. o Matt added support for optionally attaching the raw syslog message to Syslogd-generated events. o Ronny worked on refactoring/replacing our Docker test images. * *Web & UI* o I fixed some issues in the group-by-node portion of Helm's alarm details tab. <#until-next-week>Until Next Week… If there’s anything you’d like me to talk about in a future TWiO, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi <mailto:tw...@op...>. - Ben <#resolved-issues-since-last-twio>Resolved Issues Since Last TWiO * HELM-121 <https://issues.opennms.org/browse/HELM-121>: Related alarm view should show the node label * HZN-1433 <https://issues.opennms.org/browse/HZN-1433>: Update integration api to handle alarm feedback without Kafka * HZN-1441 <https://issues.opennms.org/browse/HZN-1441>: Send inventory to OCE without Kafka using integration API * HZN-1452 <https://issues.opennms.org/browse/HZN-1452>: POC of a Graph Service which tackles all existing issues with the current Topology appraoch + allows exposing graphs via Rest * NMS-9273 <https://issues.opennms.org/browse/NMS-9273>: Create Topology Service Updates in enlinkd * NMS-9659 <https://issues.opennms.org/browse/NMS-9659>: BestMatchPingerFactory returns NullPinger when better options are available * NMS-10454 <https://issues.opennms.org/browse/NMS-10454>: Support Additional EIF Protocol Version * OCE-33 <https://issues.opennms.org/browse/OCE-33>: Flag devices and ignore comparison when clock skew is detected * OCE-34 <https://issues.opennms.org/browse/OCE-34>: Match and classify CPN Tickets and OpenNMS Situations * OCE-35 <https://issues.opennms.org/browse/OCE-35>: Match CPN Events and OpenNMS Events |
From: <ma...@no...> - 2019-01-09 09:54:11
|
Hi! After upgrade to 23 opennms does not start anymore. Any ideas? An error occurred while attempting to start the "OpenNMS:Name=Eventd" service (class org.opennms.netmgt.eventd.jmx.Eventd). Shutting down and exiting. javax.management.RuntimeMBeanException: org.springframework.beans.factory.access.BootstrapException: Unable to return specified BeanFactory instance: factory key [eventDaemonContext], from group with resource name [classpath*:beanRefContext.xml]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'eventDaemonContext' defined in URL [jar:file:/opt/opennms/lib/org.opennms.features.events.daemon-23.0.1.jar!/beanRefContext.xml]: Cannot resolve reference to bean 'daoContext' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'daoContext' defined in URL [jar:file:/opt/opennms/lib/opennms-dao-23.0.1.jar!/beanRefContext.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.context.support.ClassPathXmlApplicationContext]: Constructor threw exception; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Failed to parse configuration class [org.opennms.core.ipc.rpc.kafka.ConditionalKafkaRpcContext]; nested exception is java.lang.NoSuchFieldError: KAFKA at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrow(DefaultMBeanServerInterceptor.java:839) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrowMaybeMBeanException(DefaultMBeanServerInterceptor.java:852) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:821) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) at org.opennms.netmgt.vmmgr.Invoker.invoke(Invoker.java:277) at org.opennms.netmgt.vmmgr.Invoker.invokeMethods(Invoker.java:206) at org.opennms.netmgt.vmmgr.Starter.start(Starter.java:154) at org.opennms.netmgt.vmmgr.Starter.startDaemon(Starter.java:94) at org.opennms.netmgt.vmmgr.Controller.start(Controller.java:173) at org.opennms.netmgt.vmmgr.Controller.main(Controller.java:150) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.opennms.bootstrap.Bootstrap$4.run(Bootstrap.java:525) at java.lang.Thread.run(Thread.java:745) Caused by: org.springframework.beans.factory.access.BootstrapException: Unable to return specified BeanFactory instance: factory key [eventDaemonContext], from group with resource name [classpath*:beanRefContext.xml]; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'eventDaemonContext' defined in URL [jar:file:/opt/opennms/lib/org.opennms.features.events.daemon-23.0.1.jar!/beanRefContext.xml]: Cannot resolve reference to bean 'daoContext' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'daoContext' defined in URL [jar:file:/opt/opennms/lib/opennms-dao-23.0.1.jar!/beanRefContext.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.context.support.ClassPathXmlApplicationContext]: Constructor threw exception; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Failed to parse configuration class [org.opennms.core.ipc.rpc.kafka.ConditionalKafkaRpcContext]; nested exception is java.lang.NoSuchFieldError: KAFKA at org.springframework.beans.factory.access.SingletonBeanFactoryLocator.useBeanFactory(SingletonBeanFactoryLocator.java:404) at org.opennms.core.spring.BeanUtils.getBeanFactory(BeanUtils.java:80) at org.opennms.core.spring.BeanUtils.getFactory(BeanUtils.java:132) at org.opennms.netmgt.daemon.AbstractSpringContextJmxServiceDaemon$1.run(AbstractSpringContextJmxServiceDaemon.java:103) at org.opennms.core.logging.Logging.withPrefix(Logging.java:71) at org.opennms.netmgt.daemon.AbstractSpringContextJmxServiceDaemon.init(AbstractSpringContextJmxServiceDaemon.java:96) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112) at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46) at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237) at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) ... 13 more Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'eventDaemonContext' defined in URL [jar:file:/opt/opennms/lib/org.opennms.features.events.daemon-23.0.1.jar!/beanRefContext.xml]: Cannot resolve reference to bean 'daoContext' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'daoContext' defined in URL [jar:file:/opt/opennms/lib/opennms-dao-23.0.1.jar!/beanRefContext.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.context.support.ClassPathXmlApplicationContext]: Constructor threw exception; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Failed to parse configuration class [org.opennms.core.ipc.rpc.kafka.ConditionalKafkaRpcContext]; nested exception is java.lang.NoSuchFieldError: KAFKA at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:359) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:108) at org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:648) at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:140) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1148) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1050) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:512) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202) at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1064) at org.springframework.beans.factory.access.SingletonBeanFactoryLocator.useBeanFactory(SingletonBeanFactoryLocator.java:396) ... 34 more Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'daoContext' defined in URL [jar:file:/opt/opennms/lib/opennms-dao-23.0.1.jar!/beanRefContext.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.context.support.ClassPathXmlApplicationContext]: Constructor threw exception; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Failed to parse configuration class [org.opennms.core.ipc.rpc.kafka.ConditionalKafkaRpcContext]; nested exception is java.lang.NoSuchFieldError: KAFKA at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:275) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1148) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1050) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:512) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:351) ... 47 more Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.context.support.ClassPathXmlApplicationContext]: Constructor threw exception; nested exception is org.springframework.beans.factory.BeanDefinitionStoreException: Failed to parse configuration class [org.opennms.core.ipc.rpc.kafka.ConditionalKafkaRpcContext]; nested exception is java.lang.NoSuchFieldError: KAFKA at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:163) at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:122) at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:267) ... 56 more Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Failed to parse configuration class [org.opennms.core.ipc.rpc.kafka.ConditionalKafkaRpcContext]; nested exception is java.lang.NoSuchFieldError: KAFKA at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:182) at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:321) at org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanDefinitionRegistry(ConfigurationClassPostProcessor.java:242) at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanDefinitionRegistryPostProcessors(PostProcessorRegistrationDelegate.java:273) at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:98) at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:682) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:523) at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:139) at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:105) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:422) at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:147) ... 58 more Caused by: java.lang.NoSuchFieldError: KAFKA at org.opennms.core.ipc.rpc.kafka.ConditionalKafkaRpcContext$Condition.matches(ConditionalKafkaRpcContext.java:60) at org.springframework.context.annotation.ConditionEvaluator.shouldSkip(ConditionEvaluator.java:102) at org.springframework.context.annotation.ConfigurationClassParser.processConfigurationClass(ConfigurationClassParser.java:204) at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:191) at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:174) ... 71 more 2019-01-09 10:31:47,201 ActiveMQ ShutdownHook WARN Unable to register Log4j shutdown hook because JVM is shutting down. Using SimpleLogger |
From: JohnD B. <joh...@au...> - 2019-01-08 22:28:55
|
Thanks David, I'll give that a go. - John Blackburn -----Original Message----- From: David Hustace <da...@op...> Sent: Tuesday, 8 January 2019 10:34 PM To: DiscussionList List <ope...@li...> Subject: Re: [opennms-discuss] Page Sequence Monitor to monitor a flash based website CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > On Jan 7, 2019, at 21:43, JohnD Blackburn <joh...@au...> wrote: > > After speaking with the application developers, it is possible to bypass the flash requirement, however an XML payload needs to be passed with the POST commands. Is it possible to do this with the PSM? The following *might* work. Say you wanted to POST the following XML color document: <?xml version="1.0" encoding="utf-8"?> <color name="Horizon"> <red>96</red> <green>155</green> <blue>80</blue> </color> Try this: <service name="colortest" interval="30000" user-defined="true" status="on"> <parameter key="retry" value="1"/> <parameter key="timeout" value="5000"/> <parameter key="rrd-repository" value="/opt/opennms/share/rrd/response"/> <parameter key="ds-name" value="colortest"/> <parameter key="page-sequence"> <page-sequence> <page path="/colortest" port="80" method="POST"> <parameter key="color" value="<?xml version="1.0" encoding="utf-8"?><color name="Horizon"><red>96</red><green>155</green><blue>80</blue></color>"/> </page> </page-sequence> </parameter> </service> David Hustace The OpenNMS Group, Inc. |
From: Hernandez, P. <Pau...@me...> - 2019-01-08 22:02:49
|
Hello, By referencing this doc: https://wiki.opennms.org/wiki/Enable_monitoring_of_CPU_utilization_on_Windows_systems I was able to set up CPU utilization monitoring in similar fashion on Linux hosts. My question is with regard to the use of Resource Filters and Regular Expressions via the Edit threshold form. The example in the doc above is hard-coded to assume a host has 32 cores and uses a group named “windows-host” with 32 mibObj lines. Is it possible to author a more general case solution since the more common situation is to have hosts with from 2 to 64 cores in one’s compute farm? In other words, the goal above was to define the threshold as exceeded only when all of the cores on the host exceed a given utilization. This is exactly what is desired, but what can I do, if anything. to config opennms to walk over the entire set of instances of hrProcessorLoad available for a given size host, whether it is 2 instances or 64 of them? Thanks! Paul |
From: David H. <da...@op...> - 2019-01-08 12:34:43
|
> On Jan 7, 2019, at 21:43, JohnD Blackburn <joh...@au...> wrote: > > After speaking with the application developers, it is possible to bypass the flash requirement, however an XML payload needs to be passed with the POST commands. Is it possible to do this with the PSM? The following *might* work. Say you wanted to POST the following XML color document: <?xml version="1.0" encoding="utf-8"?> <color name="Horizon"> <red>96</red> <green>155</green> <blue>80</blue> </color> Try this: <service name="colortest" interval="30000" user-defined="true" status="on"> <parameter key="retry" value="1"/> <parameter key="timeout" value="5000"/> <parameter key="rrd-repository" value="/opt/opennms/share/rrd/response"/> <parameter key="ds-name" value="colortest"/> <parameter key="page-sequence"> <page-sequence> <page path="/colortest" port="80" method="POST"> <parameter key="color" value="<?xml version="1.0" encoding="utf-8"?><color name="Horizon"><red>96</red><green>155</green><blue>80</blue></color>"/> </page> </page-sequence> </parameter> </service> David Hustace The OpenNMS Group, Inc. |
From: JohnD B. <joh...@au...> - 2019-01-08 02:58:32
|
After speaking with the application developers, it is possible to bypass the flash requirement, however an XML payload needs to be passed with the POST commands. Is it possible to do this with the PSM? From: JohnD Blackburn <joh...@au...> Sent: Tuesday, 8 January 2019 10:39 AM To: General OpenNMS Discussion <ope...@li...> Subject: [opennms-discuss] Page Sequence Monitor to monitor a flash based website CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. I'm currently using OpenNMS 23.0.1, and I'm wondering if it is possible to configure a page sequence monitor to work with a flash based site? (or if there is another way to monitor such a site.) (there is a project to move this particular application to HTML5, but I need to be able to monitor the existing flash based site until such time as the HTML 5 version is rolled out.) Regards, John Blackburn. |
From: JohnD B. <joh...@au...> - 2019-01-08 00:54:34
|
I'm currently using OpenNMS 23.0.1, and I'm wondering if it is possible to configure a page sequence monitor to work with a flash based site? (or if there is another way to monitor such a site.) (there is a project to move this particular application to HTML5, but I need to be able to monitor the existing flash based site until such time as the HTML 5 version is rolled out.) Regards, John Blackburn. |
From: Benjamin R. <ra...@op...> - 2019-01-07 19:31:51
|
It's time for This Week in OpenNMS! Last week was a little light, with some folks still out and lots of post-holiday catching up to do. We worked on alarm handling and export, and the SNMP collector. <#github-project-updates>Github Project Updates * *Internals, APIs, and Documentation* o Matt worked on improving the efficiency of incremental alarm handling in the Kafka producer. o David fixed some issues in alarm de-escalation. o Jesse updated some correlation engine documentation. o Jesse did more work on indexing alarms in Elasticsearch. o Patrick continued to work on modernizing the SNMP collector. <#dealing-with-the-javapocalypse>Dealing With the Javapocalypse <#the-current-state-of-java>The Current State of Java As you may or may not have heard, Oracle will be discontinuing public Java 8 support starting this year <https://www.oracle.com/technetwork/java/java-se-support-roadmap.html>. While there is obviously still time to transition, it is time to start talking about our plans going forward. First of all, Oracle will still be providing public updates for end users, but officially you will need to get commercial support to be supported as a commercial user starting now. Additionally, RedHat has committed to continue to support OpenJDK 8 until 2023 <https://developers.redhat.com/blog/2018/09/24/the-future-of-java-and-openjdk-updates-without-oracle-support/>. While we prefer Oracle JDK for a number of performance and scalability reasons, OpenJDK 8 has been improving steadily and should be fine for many workloads. If you will be sticking with existing Meridian releases for a while, it is a good idea to try out OpenJDK in your test environment and see if it performs well with your workload. <#next-steps>Next Steps We are currently working on support for JDK 9 and up, and hope to have it ready as part of Horizon 24. OpenNMS is running in JDK 9 in a development branch, with only a few more things that need fixing. Supporting JDK 10 and up will require some additional changes as APIs that used to be bundled with the JDK must now be provided separately. Work on that will commence as soon as JDK 9 is working smoothly. After that, we will work on making the codebase /build/ with JDK 9 and up, which is a separate, more complicated task as our build system has a lot of moving parts (and maven plugins |<grin>|). Eventually, this will turn to /requiring/ JDK 9 and up, but for now we're hoping to continue to support running OpenNMS on JDK 8 and higher. Stay tuned for more details. <#until-next-week>Until Next Week… If there’s anything you’d like me to talk about in a future TWiO, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi <mailto:tw...@op...>. - Ben <#resolved-issues-since-last-twio>Resolved Issues Since Last TWiO * NMS-10522 <https://issues.opennms.org/browse/NMS-10522>: Situation Severity is not adjusted downward as related alarms clear * NMS-10523 <https://issues.opennms.org/browse/NMS-10523>: Syslog test failures due to year offset in eventConverter |
From: Marc D. <doe...@gm...> - 2019-01-04 16:42:18
|
Hi Eduardo, That looks way more doable then manually adding all the individual assets. Thanks for pointing this out. But this does create 2 new questions :-) - What would happen if I try to add an asset that's already added to the <foreign-source> <foreign-id>. I just tested "address1" for 1 node, what would happen if I try to add "address1" again? - I tried 1 asset on 1 node and all nodes showed up again as if I did an import. But after the sync, they were all gone again. Is this normal behavior or? -- Marc D. Real is just a matter of perception On Fri, 4 Jan 2019 at 14:04, Eduardo <eco...@ju...> wrote: > Hi Marc, I asked the same question two months ago. The answer, from John > D.Blackburn is below. > > Eduardo > > You need to define the asset values in the requisition not in the node. Then when the requisition synchronizes, all the asset values get transferred to the node. > > I use the provision.pl script: > > /opt/opennms/bin/provision.pl asset set "$REQUISITION" "$FOREIGNID" "$ASSETFIELD" "$VALUE" > > Regards, > John > > > -----Original Message----- > From: Eduardo [mailto:eco...@ju... <eco...@ju...>] > Sent: Wednesday, 21 November 2018 10:45 AM > To: ope...@li... > Subject: [opennms-discuss] How to persist assets's value > > CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. > > > Hi everyone > I have an issue related with asset's data persistence. I have > provisioned all my nodes using provisioning requisitions via Web UI options. > Then I modified node's assets fields using sql queries . The problem > rise when requisitions sinchronyze, if it does all my assets updates get > lost. > > How can I keep asset's values persistent despite requisitions > synchronization ? I' ll like still use sql queries to update node's assets. > > Thanks in advance > > > Eduardo > > > > > On 4/1/19 08:30, Marc Doesburg wrote: > > Hi All, > > I'm trying to import asset data for around 50 nodes. I exported the > current asset information to a CSV file (Admin -> Import and Export > Assets), updated/added the asset data in the CSV and uploaded the new data > into OpenNMS. > > When I look at the node assets information after the import, the data is > there, icons show up on the Geo map etc. But when the Provisioning > Requisitions sync, all the imported Asset data is gone. Asset data I > entered manually (Via Provisioning Requisitions) stays in the database. > When I look at the nodes via the Provisioning Requisitions the asset data > isn't there after the import. > > So it kinda makes sense that the asset data is removed during a > Provisioning Requisition sync because as I understand it the Provisioning > Requisition overrules node asset data. And since the asset data isn't in > the Provisioning Requisitions it's removed. > > Is there an extra step I need to perform before the asset data becomes > permanent? > > -- > Marc D. > > Real is just a matter of perception > > > > ________________________________________________________________ > Note that this mailing list is not as active as other resources. > > Visit https://opennms.discourse.group/ for the forum, and > visit https://chat.opennms.com for real-time chat. > ________________________________________________________________ > > 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 > > -- > Lic. Eduardo Rodolfo Colombres > Director de Comunicaciones y Redes de datos > Secretaría de Informática Jurídica > Poder Judicial del Chubut > Tel:0280-4482333 - RPP 3333/3332 - int 141 > Cel:0280-15-4410201 > > ________________________________________________________________ > Note that this mailing list is not as active as other resources. > > Visit https://opennms.discourse.group/ for the forum, and > visit https://chat.opennms.com for real-time chat. > ________________________________________________________________ > > 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 |
From: Eduardo <eco...@ju...> - 2019-01-04 14:02:41
|
Hi Marc, I asked the same question two months ago. The answer, from John D.Blackburn is below. Eduardo You need to define the asset values in the requisition not in the node. Then when the requisition synchronizes, all the asset values get transferred to the node. I use the provision.pl script: /opt/opennms/bin/provision.pl asset set "$REQUISITION" "$FOREIGNID" "$ASSETFIELD" "$VALUE" Regards, John -----Original Message----- From: Eduardo [mailto:eco...@ju...] Sent: Wednesday, 21 November 2018 10:45 AM To:ope...@li... Subject: [opennms-discuss] How to persist assets's value CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi everyone I have an issue related with asset's data persistence. I have provisioned all my nodes using provisioning requisitions via Web UI options. Then I modified node's assets fields using sql queries . The problem rise when requisitions sinchronyze, if it does all my assets updates get lost. How can I keep asset's values persistent despite requisitions synchronization ? I' ll like still use sql queries to update node's assets. Thanks in advance Eduardo On 4/1/19 08:30, Marc Doesburg wrote: > Hi All, > > I'm trying to import asset data for around 50 nodes. I exported the > current asset information to a CSV file (Admin -> Import and Export > Assets), updated/added the asset data in the CSV and uploaded the new > data into OpenNMS. > > When I look at the node assets information after the import, the data > is there, icons show up on the Geo map etc. But when the Provisioning > Requisitions sync, all the imported Asset data is gone. Asset data I > entered manually (Via Provisioning Requisitions) stays in the > database. When I look at the nodes via the Provisioning Requisitions > the asset data isn't there after the import. > > So it kinda makes sense that the asset data is removed during a > Provisioning Requisition sync because as I understand it the > Provisioning Requisition overrules node asset data. And since the > asset data isn't in the Provisioning Requisitions it's removed. > > Is there an extra step I need to perform before the asset data becomes > permanent? > > -- > Marc D. > > Real is just a matter of perception > > > ________________________________________________________________ > Note that this mailing list is not as active as other resources. > > Visit https://opennms.discourse.group/ for the forum, and > visit https://chat.opennms.com for real-time chat. > ________________________________________________________________ > > 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 -- Lic. Eduardo Rodolfo Colombres Director de Comunicaciones y Redes de datos Secretaría de Informática Jurídica Poder Judicial del Chubut Tel:0280-4482333 - RPP 3333/3332 - int 141 Cel:0280-15-4410201 |
From: Marc D. <doe...@gm...> - 2019-01-04 13:55:37
|
Hi Michael, Thank you for your reply. And :-( Mmmmm I was afraid of that :-(. Don't really want to manually add more than 350 assets to the nodes... (That's address only...) I'll have a look to see what I can do with REST. Thanks. -- Marc D. Real is just a matter of perception On Fri, 4 Jan 2019 at 12:19, Seibold, Michael <mic...@gk...> wrote: > Hi Marc, > > > > as far as I know if you use provisioning you need to add your asset data > via provisioning, too. It should be possible per script using the > REST-Interface. The possibility to add it via import probably is a relict > from the times where there was no provisioning available. So if you add > your hosts manually or by discovery you probably can still use / you need > the asset import function, if you use provisioning you have to provision > asset data there, too. > > > > -Michael > ________________________________________________________________ > Note that this mailing list is not as active as other resources. > > Visit https://opennms.discourse.group/ for the forum, and > visit https://chat.opennms.com for real-time chat. > ________________________________________________________________ > > 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 |
From: Seibold, M. <mic...@gk...> - 2019-01-04 12:17:31
|
Hi Marc, as far as I know if you use provisioning you need to add your asset data via provisioning, too. It should be possible per script using the REST-Interface. The possibility to add it via import probably is a relict from the times where there was no provisioning available. So if you add your hosts manually or by discovery you probably can still use / you need the asset import function, if you use provisioning you have to provision asset data there, too. -Michael |
From: Marc D. <doe...@gm...> - 2019-01-04 11:31:17
|
Hi All, I'm trying to import asset data for around 50 nodes. I exported the current asset information to a CSV file (Admin -> Import and Export Assets), updated/added the asset data in the CSV and uploaded the new data into OpenNMS. When I look at the node assets information after the import, the data is there, icons show up on the Geo map etc. But when the Provisioning Requisitions sync, all the imported Asset data is gone. Asset data I entered manually (Via Provisioning Requisitions) stays in the database. When I look at the nodes via the Provisioning Requisitions the asset data isn't there after the import. So it kinda makes sense that the asset data is removed during a Provisioning Requisition sync because as I understand it the Provisioning Requisition overrules node asset data. And since the asset data isn't in the Provisioning Requisitions it's removed. Is there an extra step I need to perform before the asset data becomes permanent? -- Marc D. Real is just a matter of perception |
From: Fred <sma...@en...> - 2019-01-03 14:27:16
|
Hello, I have the same problem. Thank you, Fred > Sent: Friday, November 30, 2018 at 6:51 PM > From: "Dark Neko" <dar...@gm...> > To: "General OpenNMS Discussion" <ope...@li...> > Subject: Re: [opennms-discuss] Geocoding email > > Tried that already > > 2018-11-30T17:50:00,481 ERROR org.apache.aries.blueprint.core:1.8.3(16) [FelixStartLevel] org.apache.aries.blueprint.container.BlueprintContainerImpl: Unable to start blueprint container for bundle org.opennms.features.geocoder.nominatim/23.0.1 > org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to initialize bean nominatimGeocoderService > at org.apache.aries.blueprint.container.BeanRecipe.runBeanProcInit(BeanRecipe.java:738) [16:org.apache.aries.blueprint.core:1.8.3] > at org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(BeanRecipe.java:848) [16:org.apache.aries.blueprint.core:1.8.3] > at org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:811) [16:org.apache.aries.blueprint.core:1.8.3] > at org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:79) [16:org.apache.aries.blueprint.core:1.8.3] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:?] > at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:88) [16:org.apache.aries.blueprint.core:1.8.3] > at org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:255) [16:org.apache.aries.blueprint.core:1.8.3] > at org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:186) [16:org.apache.aries.blueprint.core:1.8.3] > at org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:704) [16:org.apache.aries.blueprint.core:1.8.3] > at org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:410) [16:org.apache.aries.blueprint.core:1.8.3] > at org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:275) [16:org.apache.aries.blueprint.core:1.8.3] > at org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:300) [16:org.apache.aries.blueprint.core:1.8.3] > at org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:269) [16:org.apache.aries.blueprint.core:1.8.3] > at org.apache.aries.blueprint.container.BlueprintExtender.createContainer(BlueprintExtender.java:265) [16:org.apache.aries.blueprint.core:1.8.3] > at org.apache.aries.blueprint.container.BlueprintExtender.modifiedBundle(BlueprintExtender.java:255) [16:org.apache.aries.blueprint.core:1.8.3] > at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:500) [16:org.apache.aries.blueprint.core:1.8.3] > at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerModified(BundleHookBundleTracker.java:433) [16:org.apache.aries.blueprint.core:1.8.3] > at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$AbstractTracked.track(BundleHookBundleTracker.java:725) [16:org.apache.aries.blueprint.core:1.8.3] > at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.bundleChanged(BundleHookBundleTracker.java:463) [16:org.apache.aries.blueprint.core:1.8.3] > at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$BundleEventHook.event(BundleHookBundleTracker.java:422) [16:org.apache.aries.blueprint.core:1.8.3] > at org.apache.felix.framework.util.SecureAction.invokeBundleEventHook(SecureAction.java:1179) [?:?] > at org.apache.felix.framework.EventDispatcher.createWhitelistFromHooks(EventDispatcher.java:730) [?:?] > at org.apache.felix.framework.EventDispatcher.fireBundleEvent(EventDispatcher.java:485) [?:?] > at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4579) [?:?] > at org.apache.felix.framework.Felix.startBundle(Felix.java:2174) [?:?] > at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1373) [?:?] > at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:308) [?:?] > at java.lang.Thread.run(Thread.java:748) [?:?] > Caused by: java.lang.UnsupportedOperationException: You must specify an email address for the Nominatim geocoder! > at org.opennms.features.geocoder.nominatim.NominatimGeocoderService.onInit(NominatimGeocoderService.java:72) ~[?:?] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?] > at java.lang.reflect.Method.invoke(Method.java:498) ~[?:?] > at org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:299) ~[?:?] > at org.apache.aries.blueprint.container.BeanRecipe.invoke(BeanRecipe.java:980) ~[?:?] > at org.apache.aries.blueprint.container.BeanRecipe.runBeanProcInit(BeanRecipe.java:736) ~[?:?] > ... 27 more > > > content of my opennms properties file: > > # The rate at which to make requests, for geocoders that support it. > gwt.geocoder.rate=10 > # The referer to use when making geocoding requests, for geocoders that support it. > gwt.geocoder.minimumQuality=ZIP > gwt.geocoder.email=<my email> > gwt.geocoder.class=org.opennms.features.poller.remote.gwt.server.geocoding.NominatimGeocoder > > Envoyé de mon iPhone > > > Le 30 nov. 2018 à 16:59, David Hustace <da...@op...> a écrit : > > > > > > > >> On Nov 30, 2018, at 08:58, Dark Neko <dar...@gm...> wrote: > >> > >> What I am missing? > > > > Restart? > > > > David > > > > > > > > David Hustace > > The OpenNMS Group, Inc. > > > > > > _______________________________________________ > > 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 > > > _______________________________________________ > 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 |
From: Hernandez, P. <Pau...@me...> - 2019-01-02 19:06:10
|
HNY all, With regard to: https://issues.opennms.org/browse/NMS-7676 Any idea when this hugely import item might be assigned? Many thanks, Paul From: Benjamin Reed [mailto:ra...@op...] Sent: Wednesday, January 2, 2019 10:47 AM To: OpenNMS Announcements <ope...@li...>; General OpenNMS Discussion <ope...@li...> Subject: [opennms-discuss] This Week in OpenNMS - January 2nd, 2019 - Refactoring, Modernization, and the New Year! 🎉 It's time for This Week in OpenNMS! We're back! And this time, it's personal. In the last few weeks we did lots of refactoring and cleanup and continued some projects that were in-progress. Github Project Updates · Internals, APIs, and Documentation * Jesse and David did more work on indexing alarms in Elasticsearch. * Markus did more work on cleaning up imports in our code. * Jesse fixed a potential deadlock in reloading the Drools context in Alarmd. * Patrick continued his work on modernizing the SNMP collector codebase. * Patrick did more refactoring of integer parsing in our codebase. * Matt worked on fixing some potential concurrent modification exceptions in OSGi service binding. * I worked on fixing the BestMatchPingerFactory to use the loopback address to test validity on startup. * Dustin updated flow classification to handle omnidirectional flows. * I refactored the opennms script to fix all shellcheck warnings. * Markus worked on fixing potential OOM issues in the daemon refactor branch. * I did a bunch of work to get OpenNMS running under Java 9. * David worked on prioritization of event definitions. * I worked on updating our database upgrade infrastructure to Liquibase 3. * Antonio worked on pushing topology data to Kafka. · Web & UI * Dustin refactored his work on browser notifications a bit. * Sebastian continued to work on the Bootstrap 4 UI migration. * Antonio continued his work on a link and topology refactor. Until Next Week… If there’s anything you’d like me to talk about in a future TWiO, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi<mailto:tw...@op...>. - Ben Resolved Issues Since Last TWiO * HZN-1419<https://issues.opennms.org/browse/HZN-1419>: Add support for prioritizing the event definitions * HZN-1450<https://issues.opennms.org/browse/HZN-1450>: Add example on how to use Drools with alarms for nagging events * HZN-1451<https://issues.opennms.org/browse/HZN-1451>: Prevent CME in OSGI service binding * NMS-10369<https://issues.opennms.org/browse/NMS-10369>: Performance problems with the Topology Map on large networks * NMS-10465<https://issues.opennms.org/browse/NMS-10465>: Event configuration should be able to match event parameters by key & value * NMS-10495<https://issues.opennms.org/browse/NMS-10495>: linkDown alarms are not generated for unknown ifIndex values * NMS-10509<https://issues.opennms.org/browse/NMS-10509>: Harden Drools engine in alarmd |