Hello again,
Thanks for the eyes on this!
Understood regarding the "back-end process" and thank you for that insight.
To be clear, the "status displays" (EG: Service Status Summary, under HOME section) section expose the "last known results" for the proper nodes that have matching NRDP rules to feed them (with my USER view, as well as with my ADMIN user).
This appears to be a visibility challenge within the CCM sub-section itself, under the CCM: Monitoring > Service section (where it is not visible for a LIMITED user, but is for an ADMIN user).
Our ORG wishes to enable the USER persons to be able to work on these, without making them ADMIN users.
I have detailed our present USER (LIMITED) permissions config at the bottom of my initial post, if this is relevant.
At present we have the following counts (going by the view in CCM Object Summary).
These numbers come from what is to be our PROD environment instance, where at present the users are performing testing ahead of offical cut-over from our legacy product.
Thus, I would expect these numbers to go up in some areas (EG: hosts count).
Code: Select all
Hosts: 145
Host Groups: 20
Services: 30
Service Groups: 0
Contacts: 76
Contact Groups: 16
For context, we have positioned our strategy as follows:
Active checks:
UP/DOWN (check_ping) active checks (via a host template), will grow as more nodes are added (several thousand once fully cut-over to this application)
We are likely add a select few other Active checks, like a hand-ful of URL monitors.
Passive checks:
Everything else.
NCPA agent layered on monitored nodes, NRDP rules used to "call home" when there is an issue to alert upon.
We are really pushing folks to stay away from Active checks (and the wizards) to minimize load on XI, and delegate that to the nodes (via NCPA & passive checks).
How long does it take (time it) from apply config until it's finally viewable by the user?
This is the base issue from my user's perspective, as it *never shows up* (or delay / lag time appears as "infinite" in its visibility to non-ADMIN users).
For example, one of my users will create an entry and days have gone by without it becoming visible to them.
In my triage re-production attempts this past morning, my test user (no ADMIN perms) created a Service definition (CCM: Monitoring > Services > Add New), which then disappears from visibility at commit screen (either after you commit, or if you "go to another page and then try to Apply Config).
Users with the ADMIN permission, continue to see the new service definition without challenge (no interruption of visibility).
It feels like some sort of failure to complete the "CCM permissions building process", where perhaps the object visibility permissions are somehow not being properly generated/applied?
What about for an admin?
It appears almost instantly for an ADMIN level user.
Specific timing is: ~30 seconds from clicking "apply config" to successful commit screen, than it is ready within another 30 seconds for ADMIN user visibility (hand timing).
I have the Profile to submit to you.
Where may I put it for you, without uploading to the forum thread?
As requested, here is the output (dB off-box):
Code: Select all
MariaDB [(none)]> SELECT table_name AS 'Table', round(((data_length + index_length) / 1024 / 1024), 2) 'Size in MB' FROM information_schema.TABLES WHERE table_schema IN ('nagios', 'nagiosql', 'nagiosxi');
+--------------------------------------------+------------+
| Table | Size in MB |
+--------------------------------------------+------------+
| nagios_acknowledgements | 0.00 |
| nagios_commands | 0.02 |
| nagios_commenthistory | 0.73 |
| nagios_comments | 0.00 |
| nagios_configfiles | 0.00 |
| nagios_configfilevariables | 0.01 |
| nagios_conninfo | 0.10 |
| nagios_contact_addresses | 0.00 |
| nagios_contact_notificationcommands | 0.04 |
| nagios_contactgroup_members | 0.01 |
| nagios_contactgroups | 0.00 |
| nagios_contactnotificationmethods | 2.00 |
| nagios_contactnotifications | 2.44 |
| nagios_contacts | 0.01 |
| nagios_contactstatus | 0.01 |
| nagios_customvariables | 0.02 |
| nagios_customvariablestatus | 0.02 |
| nagios_dbversion | 0.00 |
| nagios_downtimehistory | 0.01 |
| nagios_eventhandlers | 0.00 |
| nagios_externalcommands | 0.00 |
| nagios_flappinghistory | 0.01 |
| nagios_host_contactgroups | 0.01 |
| nagios_host_contacts | 0.01 |
| nagios_host_parenthosts | 0.00 |
| nagios_hostchecks | 0.00 |
| nagios_hostdependencies | 0.00 |
| nagios_hostescalation_contactgroups | 0.00 |
| nagios_hostescalation_contacts | 0.00 |
| nagios_hostescalations | 0.00 |
| nagios_hostgroup_members | 0.02 |
| nagios_hostgroups | 0.00 |
| nagios_hosts | 0.04 |
| nagios_hoststatus | 0.10 |
| nagios_instances | 0.00 |
| nagios_logentries | 154.19 |
| nagios_notifications | 3.00 |
| nagios_objects | 0.27 |
| nagios_processevents | 0.24 |
| nagios_programstatus | 0.00 |
| nagios_runtimevariables | 0.00 |
| nagios_scheduleddowntime | 0.00 |
| nagios_service_contactgroups | 0.01 |
| nagios_service_contacts | 0.05 |
| nagios_service_parentservices | 0.00 |
| nagios_servicechecks | 0.00 |
| nagios_servicedependencies | 0.00 |
| nagios_serviceescalation_contactgroups | 0.00 |
| nagios_serviceescalation_contacts | 0.00 |
| nagios_serviceescalations | 0.00 |
| nagios_servicegroup_members | 0.00 |
| nagios_servicegroups | 0.00 |
| nagios_services | 0.22 |
| nagios_servicestatus | 0.95 |
| nagios_statehistory | 1.87 |
| nagios_systemcommands | 0.03 |
| nagios_timedeventqueue | 0.00 |
| nagios_timedevents | 0.00 |
| nagios_timeperiod_timeranges | 0.03 |
| nagios_timeperiods | 0.01 |
| tbl_command | 0.06 |
| tbl_contact | 0.03 |
| tbl_contactgroup | 0.03 |
| tbl_contacttemplate | 0.03 |
| tbl_domain | 0.03 |
| tbl_host | 0.06 |
| tbl_hostdependency | 0.03 |
| tbl_hostescalation | 0.03 |
| tbl_hostextinfo | 0.03 |
| tbl_hostgroup | 0.03 |
| tbl_hosttemplate | 0.03 |
| tbl_info | 0.17 |
| tbl_lnkContactToCommandHost | 0.02 |
| tbl_lnkContactToCommandService | 0.02 |
| tbl_lnkContactToContactgroup | 0.02 |
| tbl_lnkContactToContacttemplate | 0.02 |
| tbl_lnkContactToVariabledefinition | 0.02 |
| tbl_lnkContactgroupToContact | 0.02 |
| tbl_lnkContactgroupToContactgroup | 0.02 |
| tbl_lnkContacttemplateToCommandHost | 0.02 |
| tbl_lnkContacttemplateToCommandService | 0.02 |
| tbl_lnkContacttemplateToContactgroup | 0.02 |
| tbl_lnkContacttemplateToContacttemplate | 0.02 |
| tbl_lnkContacttemplateToVariabledefinition | 0.02 |
| tbl_lnkHostToContact | 0.02 |
| tbl_lnkHostToContactgroup | 0.02 |
| tbl_lnkHostToHost | 0.02 |
| tbl_lnkHostToHostgroup | 0.02 |
| tbl_lnkHostToHosttemplate | 0.02 |
| tbl_lnkHostToVariabledefinition | 0.02 |
| tbl_lnkHostdependencyToHost_DH | 0.02 |
| tbl_lnkHostdependencyToHost_H | 0.02 |
| tbl_lnkHostdependencyToHostgroup_DH | 0.02 |
| tbl_lnkHostdependencyToHostgroup_H | 0.02 |
| tbl_lnkHostescalationToContact | 0.02 |
| tbl_lnkHostescalationToContactgroup | 0.02 |
| tbl_lnkHostescalationToHost | 0.02 |
| tbl_lnkHostescalationToHostgroup | 0.02 |
| tbl_lnkHostgroupToHost | 0.02 |
| tbl_lnkHostgroupToHostgroup | 0.02 |
| tbl_lnkHosttemplateToContact | 0.02 |
| tbl_lnkHosttemplateToContactgroup | 0.02 |
| tbl_lnkHosttemplateToHost | 0.02 |
| tbl_lnkHosttemplateToHostgroup | 0.02 |
| tbl_lnkHosttemplateToHosttemplate | 0.02 |
| tbl_lnkHosttemplateToVariabledefinition | 0.02 |
| tbl_lnkServiceToContact | 0.02 |
| tbl_lnkServiceToContactgroup | 0.02 |
| tbl_lnkServiceToHost | 0.02 |
| tbl_lnkServiceToHostgroup | 0.02 |
| tbl_lnkServiceToServicegroup | 0.02 |
| tbl_lnkServiceToServicetemplate | 0.02 |
| tbl_lnkServiceToVariabledefinition | 0.02 |
| tbl_lnkServicedependencyToHost_DH | 0.02 |
| tbl_lnkServicedependencyToHost_H | 0.02 |
| tbl_lnkServicedependencyToHostgroup_DH | 0.02 |
| tbl_lnkServicedependencyToHostgroup_H | 0.02 |
| tbl_lnkServicedependencyToService_DS | 0.02 |
| tbl_lnkServicedependencyToService_S | 0.02 |
| tbl_lnkServicedependencyToServicegroup_DS | 0.02 |
| tbl_lnkServicedependencyToServicegroup_S | 0.02 |
| tbl_lnkServiceescalationToContact | 0.02 |
| tbl_lnkServiceescalationToContactgroup | 0.02 |
| tbl_lnkServiceescalationToHost | 0.02 |
| tbl_lnkServiceescalationToHostgroup | 0.02 |
| tbl_lnkServiceescalationToService | 0.02 |
| tbl_lnkServiceescalationToServicegroup | 0.02 |
| tbl_lnkServicegroupToService | 0.02 |
| tbl_lnkServicegroupToServicegroup | 0.02 |
| tbl_lnkServicetemplateToContact | 0.02 |
| tbl_lnkServicetemplateToContactgroup | 0.02 |
| tbl_lnkServicetemplateToHost | 0.02 |
| tbl_lnkServicetemplateToHostgroup | 0.02 |
| tbl_lnkServicetemplateToServicegroup | 0.02 |
| tbl_lnkServicetemplateToServicetemplate | 0.02 |
| tbl_lnkServicetemplateToVariabledefinition | 0.02 |
| tbl_lnkTimeperiodToTimeperiod | 0.02 |
| tbl_logbook | 0.02 |
| tbl_mainmenu | 0.02 |
| tbl_permission | 0.06 |
| tbl_permission_inactive | 0.02 |
| tbl_service | 0.02 |
| tbl_servicedependency | 0.03 |
| tbl_serviceescalation | 0.03 |
| tbl_serviceextinfo | 0.03 |
| tbl_servicegroup | 0.03 |
| tbl_servicetemplate | 0.03 |
| tbl_session | 0.02 |
| tbl_session_locks | 0.02 |
| tbl_settings | 0.03 |
| tbl_submenu | 0.02 |
| tbl_timedefinition | 0.05 |
| tbl_timeperiod | 0.03 |
| tbl_user | 0.03 |
| tbl_variabledefinition | 0.02 |
| xi_auditlog | 2.17 |
| xi_auth_tokens | 1.58 |
| xi_cmp_trapdata | 0.03 |
| xi_cmp_trapdata_log | 0.03 |
| xi_commands | 0.02 |
| xi_eventqueue | 0.03 |
| xi_events | 0.09 |
| xi_meta | 1.52 |
| xi_mibs | 0.05 |
| xi_options | 0.06 |
| xi_sessions | 0.03 |
| xi_sysstat | 0.03 |
| xi_usermeta | 0.63 |
| xi_users | 0.06 |
+--------------------------------------------+------------+
169 rows in set (0.01 sec)
Code: Select all
MariaDB [nagios]> SELECT count(*) FROM nagios_objects;
+----------+
| count(*) |
+----------+
| 2620 |
+----------+
1 row in set (0.00 sec)
What version of XI are you running? There were some recent changes that should speed up some of that in the latest versions.
# ENV
Code: Select all
OS: RHEL 7.x (VMWare)
Nagios Core: 4.4.3
Nagios XI: 5.6.6
Nagios dB: 5.5.64-MariaDB MariaDB Server (off-box)
Attach your /etc/php.ini as well and we will see if we can increase some of the limits for a little better performance.
Attached for your review.
Thanks for your efforts on this!
EDIT:
I have sent the 'profile.zip' file from my XI-PROD ENV to ssax via PM.
You do not have the required permissions to view the files attached to this post.
