Issues
- HostResourceSwRunMonitor: define the service-name parameter as a regular expressionNMS-4978Resolved issue: NMS-4978Alejandro Galue
- Notifications Fail with IPv6 AddressesNMS-4977Resolved issue: NMS-4977Matt Brozowski
- Exception with ldapAuthoritiesPopulator with LDAP and / or Radius integrationNMS-4975Resolved issue: NMS-4975Jeff Gehlbach
- Configuring SNMP broken for biggish IPv4 rangesNMS-4972Resolved issue: NMS-4972Alejandro Galue
- Building 1.10-branch on Lion seems to crashNMS-4969Resolved issue: NMS-4969Benjamin Reed
- All SNMP Interfaces marked as "no collect" by default on any provisioned nodeNMS-4965Resolved issue: NMS-4965Matt Brozowski
- Create a table view for the provisioning Group pageNMS-4964
- Asset-page categorie fields validation.NMS-4963Resolved issue: NMS-4963Markus Neumann
- Asset-page shows rancid password readable. Change to password fields.NMS-4961Resolved issue: NMS-4961Markus Neumann
- http://xmlns.opennms.org/xsd/ spits out wrong MIME typeNMS-4960
- KSC Child Resource List is not in alphabetical orderNMS-4957Resolved issue: NMS-4957Donald Desloge
- KSC Overall Report Menu Formatted StrangelyNMS-4956Resolved issue: NMS-4956Donald Desloge
- Scheduled outages webui does not validate input, produces exceptionsNMS-4952
- Create button icons for individual operating systems for the node page.NMS-4944
- No working breadcrumb on System Report List PageNMS-4943Resolved issue: NMS-4943Markus Neumann
- default graph definition GPRINT spacing is too wideNMS-4941
- Hung threads causing 100% CPU usage (possibly Jetty + HTTPS/SSL related)NMS-4940Resolved issue: NMS-4940Donald Desloge
- many default graph definitions include unreferenced min/max DEFs and CDEFsNMS-4939Tarus Balog
- Default GC and fullGC automations clash with alarm-driven status view in topo mapNMS-4932Jeff Gehlbach
- Availability Miscalculated in NodeAvailabilityReport.jrxml (and others)NMS-4931Resolved issue: NMS-4931Donald Desloge
- node.jsp - Node Interfaces only displays up to 20 interfacesNMS-4929Resolved issue: NMS-4929Donald Desloge
- RadiusAuthenticationProvider.java Tests against wrong variable.NMS-4928Resolved issue: NMS-4928Alejandro Galue
- Deletion of surveillance categories via WebUI is brokenNMS-4927Resolved issue: NMS-4927Benjamin Reed
- KSC Reports search box on home page is case sensitiveNMS-4922Resolved issue: NMS-4922Donald Desloge
- Resource Graphs selector - doesn't indicate stale graph dataNMS-4918Resolved issue: NMS-4918Donald Desloge
- LDAP group authorization ignores convertToUpperCase propertyNMS-4874
- With Jetty + HTTPS, certain Web UI actions prompt browser to "Save As" JSP and HTML filesNMS-4871Resolved issue: NMS-4871Donald Desloge
27 of 27
HostResourceSwRunMonitor: define the service-name parameter as a regular expression
Fixed
Description
Acceptance / Success Criteria
None
Lucidchart Diagrams
Created October 11, 2011 at 12:52 PM
Updated January 27, 2017 at 4:19 PM
Resolved October 11, 2011 at 1:00 PM
Activity
Show:
Alejandro GalueOctober 11, 2011 at 1:00 PM
I've committed the solution for both branches (1.8 and 1.10), on the following revisions:
1.8: 11d8298fb7ac3048e3234c5c560859a78a049d3d
1.10: ef830a77aa0af40514be4a3ab097ca2e697f48b6
For 1.8, I've also included some additional features already available on 1.10 for this particular monitor:
a) remove the extra quotes, and when no regex is defined
b) use "equalsIgnoreCase" instead of "equals" when comparing the service-name.
Here is an example usage:
The service GDM-SIMPLE will scan all the running software on the target machine where their name matches regex "^gdm-.*" (without the quotes), and will be available if the match count is greater or equal and 2 and less or equal than 5.
It could be very useful to define the service-name parameter used by the HostResourceSwRunMonitor.java to be a regular expression when matching the software running in the remote machine, like
N[tT][rR][tT][Ss]can.exe
Also, If "match-all" is true, there can be an optional "min-services" and "max-services" parameters that can define a range. The service is up if:
a) services_count >= min-services and services_count <= max-services
b) either one is not defined, then only one has to pass.
c) neither are defined, the monitor acts just like it used to - checking
All instances to see if they are all running. It is assumed that all services would have to pass the minimum run state test, no matter what the count.