Page 1 of 2
First notification = Escalation l2
Posted: Fri Aug 24, 2018 9:08 am
by chrtap
Hi,
In the attachment, I give you the configuration used for a service with escalation. When a problem arrived, immediately when a hard critical stat was checked, the notification corresponding of escalation level 2 was sent. Escalation level 1 and service notification was never sent.
More than that, when I wanted to understand what happened, I saw that I can't view State history of services and hosts (even if I use reports). I can view services (and hosts) notifications, but not State history.
To view states history I have to go to "View in Nagios Core" or as an admin user I can read "Audit log".
Could you help me ?
Re: First notification = Escalation l2
Posted: Fri Aug 24, 2018 11:05 am
by npolovenko
Hello,
@chrtap. What version of XI are you currently running? Can you show me the config for the service escalation? What happens when you're trying to view the State history report? Is it taking too long to load?
Also, It would be helpful to look into your system profile. To send us your system profile. Login to the Nagios XI GUI using a web browser.
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button
Save the profile.zip file and upload it to a cloud storage of your choice. You can share a link with me in a personal message.
After you upload the profile please post something in this thread to bring it up in the support queue.
Re: First notification = Escalation l2
Posted: Mon Aug 27, 2018 6:30 am
by chrtap
Hello,
What version of XI are you currently running?
We are running, actually, NagiosXI 5.5.2.
Can you show me the config for the service escalation?
In attached PDF, I gave print screen of configuration for service and the two escalations.
Here is an extract from the configuration file :
define serviceescalation {
# config_name OTRS01_lv1
host_name OTRS01
service_description Check old file ECM Input
contact_groups SAP-admins-SMS
first_notification 2
last_notification 2
notification_interval 60
escalation_period MediumTime
escalation_options w,c,u,r
}
define serviceescalation {
# config_name OTRS01_lv2
host_name OTRS01
service_description Check old file ECM Input
contact_groups piquet,SAP-admins-SMS
first_notification 3
last_notification 0
notification_interval 480
escalation_period MediumTime
escalation_options w,c,r
}
What happens when you're trying to view the State history report? Is it taking too long to load?
Answer is very fast but it's nothing in the list see attachment (2018-08-27_13h01_01.png)
Maybe in rapport I found errors in
/var/log/messages
Aug 27 13:06:38 monitor01 ndo2db: Error: mysql_query() failed for 'INSERT INTO nagios_statehistory SET instance_id='1', state_time=FROM_UNIXTIME(1535367998), state_time_usec='235971', object_id='5240', state_change='1', state='0', state_type='0', current_check_attempt='1', max_check_attempts='5', last_state='1', last_hard_state='0', output='OK: Percent was 2\.00 %, 21\.60 %, 23\.80 %, 22\.20 %', long_output='''
You will find profile.zip in
https://webtransfer.vs.ch/en/download/0 ... 53d62a43b2
I'll give you the password in a personal message.
Regards.
Re: First notification = Escalation l2
Posted: Mon Aug 27, 2018 3:15 pm
by ssax
npolovenko is out of the office today, please PM me the password for your profile.
Also, please send the output of this command:
Code: Select all
echo "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');" | mysql -uroot -pnagiosxi --table
Re: First notification = Escalation l2
Posted: Wed Aug 29, 2018 7:02 am
by chrtap
Hi,
The output asked :
echo "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');" | mysql -uroot -pnagiosxi --table
+--------------------------------------------+------------+
| Table | Size in MB |
+--------------------------------------------+------------+
| nagios_acknowledgements | 0.11 |
| nagios_commands | 0.05 |
| nagios_commenthistory | 4.13 |
| nagios_comments | 0.01 |
| nagios_configfiles | 0.00 |
| nagios_configfilevariables | 0.01 |
| nagios_conninfo | 0.39 |
| nagios_contact_addresses | 0.00 |
| nagios_contact_notificationcommands | 0.07 |
| nagios_contactgroup_members | 0.01 |
| nagios_contactgroups | 0.00 |
| nagios_contactnotificationmethods | 12.03 |
| nagios_contactnotifications | 12.75 |
| nagios_contacts | 0.02 |
| nagios_contactstatus | 0.01 |
| nagios_customvariables | 0.06 |
| nagios_customvariablestatus | 0.06 |
| nagios_dbversion | 0.00 |
| nagios_downtimehistory | 0.38 |
| nagios_eventhandlers | 0.04 |
| nagios_externalcommands | 0.09 |
| nagios_flappinghistory | 2.39 |
| nagios_host_contactgroups | 0.04 |
| nagios_host_contacts | 0.00 |
| 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.01 |
| nagios_hostgroups | 0.00 |
| nagios_hosts | 0.19 |
| nagios_hoststatus | 0.42 |
| nagios_instances | 0.00 |
| nagios_logentries | 272.95 |
| nagios_notifications | 38.98 |
| nagios_objects | 1.66 |
| nagios_processevents | 0.35 |
| nagios_programstatus | 0.00 |
| nagios_runtimevariables | 0.00 |
| nagios_scheduleddowntime | 0.00 |
| nagios_service_contactgroups | 0.29 |
| nagios_service_contacts | 0.01 |
| nagios_service_parentservices | 0.00 |
| nagios_servicechecks | 0.00 |
| nagios_servicedependencies | 0.00 |
| nagios_serviceescalation_contactgroups | 0.03 |
| nagios_serviceescalation_contacts | 0.01 |
| nagios_serviceescalations | 0.03 |
| nagios_servicegroup_members | 0.01 |
| nagios_servicegroups | 0.00 |
| nagios_services | 1.02 |
| nagios_servicestatus | 2.83 |
| nagios_statehistory | 253.86 |
| nagios_systemcommands | 0.04 |
| nagios_timedeventqueue | 0.00 |
| nagios_timedevents | 0.00 |
| nagios_timeperiod_timeranges | 0.04 |
| nagios_timeperiods | 0.01 |
| tbl_command | 0.07 |
| tbl_contact | 0.02 |
| tbl_contactgroup | 0.01 |
| tbl_contacttemplate | 0.01 |
| tbl_domain | 0.01 |
| tbl_host | 0.19 |
| tbl_hostdependency | 0.00 |
| tbl_hostescalation | 0.01 |
| tbl_hostextinfo | 0.00 |
| tbl_hostgroup | 0.01 |
| tbl_hosttemplate | 0.01 |
| tbl_info | 0.13 |
| tbl_lnkContactToCommandHost | 0.00 |
| tbl_lnkContactToCommandService | 0.00 |
| tbl_lnkContactToContactgroup | 0.00 |
| tbl_lnkContactToContacttemplate | 0.01 |
| tbl_lnkContactToVariabledefinition | 0.00 |
| tbl_lnkContactgroupToContact | 0.01 |
| tbl_lnkContactgroupToContactgroup | 0.00 |
| tbl_lnkContacttemplateToCommandHost | 0.00 |
| tbl_lnkContacttemplateToCommandService | 0.00 |
| tbl_lnkContacttemplateToContactgroup | 0.00 |
| tbl_lnkContacttemplateToContacttemplate | 0.00 |
| tbl_lnkContacttemplateToVariabledefinition | 0.00 |
| tbl_lnkHostToContact | 0.00 |
| tbl_lnkHostToContactgroup | 0.03 |
| tbl_lnkHostToHost | 0.00 |
| tbl_lnkHostToHostgroup | 0.00 |
| tbl_lnkHostToHosttemplate | 0.01 |
| tbl_lnkHostToVariabledefinition | 0.00 |
| tbl_lnkHostdependencyToHost_DH | 0.00 |
| tbl_lnkHostdependencyToHost_H | 0.00 |
| tbl_lnkHostdependencyToHostgroup_DH | 0.00 |
| tbl_lnkHostdependencyToHostgroup_H | 0.00 |
| tbl_lnkHostescalationToContact | 0.00 |
| tbl_lnkHostescalationToContactgroup | 0.00 |
| tbl_lnkHostescalationToHost | 0.00 |
| tbl_lnkHostescalationToHostgroup | 0.00 |
| tbl_lnkHostgroupToHost | 0.00 |
| tbl_lnkHostgroupToHostgroup | 0.00 |
| tbl_lnkHosttemplateToContact | 0.00 |
| tbl_lnkHosttemplateToContactgroup | 0.00 |
| tbl_lnkHosttemplateToHost | 0.00 |
| tbl_lnkHosttemplateToHostgroup | 0.00 |
| tbl_lnkHosttemplateToHosttemplate | 0.00 |
| tbl_lnkHosttemplateToVariabledefinition | 0.00 |
| tbl_lnkServiceToContact | 0.01 |
| tbl_lnkServiceToContactgroup | 0.17 |
| tbl_lnkServiceToHost | 0.14 |
| tbl_lnkServiceToHostgroup | 0.00 |
| tbl_lnkServiceToServicegroup | 0.00 |
| tbl_lnkServiceToServicetemplate | 0.02 |
| tbl_lnkServiceToVariabledefinition | 0.02 |
| tbl_lnkServicedependencyToHost_DH | 0.00 |
| tbl_lnkServicedependencyToHost_H | 0.00 |
| tbl_lnkServicedependencyToHostgroup_DH | 0.00 |
| tbl_lnkServicedependencyToHostgroup_H | 0.00 |
| tbl_lnkServicedependencyToService_DS | 0.00 |
| tbl_lnkServicedependencyToService_S | 0.00 |
| tbl_lnkServiceescalationToContact | 0.00 |
| tbl_lnkServiceescalationToContactgroup | 0.02 |
| tbl_lnkServiceescalationToHost | 0.01 |
| tbl_lnkServiceescalationToHostgroup | 0.00 |
| tbl_lnkServiceescalationToService | 0.01 |
| tbl_lnkServicegroupToService | 0.01 |
| tbl_lnkServicegroupToServicegroup | 0.00 |
| tbl_lnkServicetemplateToContact | 0.00 |
| tbl_lnkServicetemplateToContactgroup | 0.00 |
| tbl_lnkServicetemplateToHost | 0.00 |
| tbl_lnkServicetemplateToHostgroup | 0.00 |
| tbl_lnkServicetemplateToServicegroup | 0.00 |
| tbl_lnkServicetemplateToServicetemplate | 0.01 |
| tbl_lnkServicetemplateToVariabledefinition | 0.00 |
| tbl_lnkTimeperiodToTimeperiod | 0.00 |
| tbl_logbook | 0.01 |
| tbl_mainmenu | 0.00 |
| tbl_permission | 0.02 |
| tbl_permission_inactive | 0.02 |
| tbl_service | 0.91 |
| tbl_servicedependency | 0.00 |
| tbl_serviceescalation | 0.04 |
| tbl_serviceextinfo | 0.00 |
| tbl_servicegroup | 0.01 |
| tbl_servicetemplate | 0.02 |
| tbl_session | 0.00 |
| tbl_session_locks | 0.00 |
| tbl_settings | 0.00 |
| tbl_submenu | 0.00 |
| tbl_timedefinition | 0.03 |
| tbl_timeperiod | 0.02 |
| tbl_user | 0.01 |
| tbl_variabledefinition | 0.04 |
+--------------------------------------------+------------+
I will send you the password in a private message.
Regards.
Re: First notification = Escalation l2
Posted: Wed Aug 29, 2018 2:45 pm
by ssax
The password says it's invalid
Re: First notification = Escalation l2
Posted: Fri Aug 31, 2018 10:08 am
by chrtap
Hi,
Ok. I will be on holiday for the next 3 weeks. I will send you a new password when I'm back and and we can continue the investigations
Regards.
Re: First notification = Escalation l2
Posted: Fri Aug 31, 2018 1:39 pm
by ssax
Sounds good, thank you.
Re: First notification = Escalation l2
Posted: Mon Oct 22, 2018 9:46 am
by chrtap
Hi,
Return holiday, I forgot this case. Some one can help me ?
regards.
Re: First notification = Escalation l2
Posted: Mon Oct 22, 2018 2:07 pm
by ssax
We need a copy of your profile so that we can look through your configuration/logs. Please PM it to one of us so that we can review it.
Thank you