Comments are not persistent?
akadoya opened this issue · comments
livestatus API is not exposing the persistent comments after reloading/restarting arbiter although the shinken UI shows the comments/downtimes.
Is this expected behavior for simple-log? if so, which backend would work to keep the persistent data for comments and downtimes?
shinken1:/tmp# curl -i -X POST http://localhost:50000/query -H "Content-Type: text/xml" --data-binary "@/tmp/query"
author;comment;entry_time;entry_type;expire_time;expires;host_accept_passive_checks;host_acknowledged;host_acknowledgement_type;host_action_url;host_action_url_expanded;host_active_checks_enabled;host_address;host_alias;host_check_command;host_check_flapping_recovery_notification;host_check_freshness;host_check_interval;host_check_options;host_check_period;host_check_type;host_checks_enabled;host_childs;host_comments;host_comments_with_info;host_contact_groups;host_contacts;host_current_attempt;host_current_notification_number;host_custom_variable_names;host_custom_variable_values;host_custom_variables;host_display_name;host_downtimes;host_downtimes_with_info;host_event_handler_enabled;host_execution_time;host_filename;host_first_notification_delay;host_flap_detection_enabled;host_groups;host_hard_state;host_has_been_checked;host_high_flap_threshold;host_icon_image;host_icon_image_alt;host_icon_image_expanded;host_in_check_period;host_in_notification_period;host_initial_state;host_is_executing;host_is_flapping;host_last_check;host_last_hard_state;host_last_hard_state_change;host_last_notification;host_last_state;host_last_state_change;host_last_time_down;host_last_time_unreachable;host_last_time_up;host_latency;host_long_plugin_output;host_low_flap_threshold;host_max_check_attempts;host_modified_attributes;host_modified_attributes_list;host_name;host_next_check;host_next_notification;host_no_more_notifications;host_notes;host_notes_expanded;host_notes_url;host_notes_url_expanded;host_notification_interval;host_notification_period;host_notifications_enabled;host_num_services;host_num_services_crit;host_num_services_hard_crit;host_num_services_hard_ok;host_num_services_hard_unknown;host_num_services_hard_warn;host_num_services_ok;host_num_services_pending;host_num_services_unknown;host_num_services_warn;host_obsess_over_host;host_parents;host_pending_flex_downtime;host_percent_state_change;host_perf_data;host_plugin_output;host_pnpgraph_present;host_process_performance_data;host_retry_interval;host_scheduled_downtime_depth;host_services;host_services_with_info;host_services_with_state;host_state;host_state_type;host_statusmap_image;host_total_services;host_worst_service_hard_state;host_worst_service_state;host_x_3d;host_y_3d;host_z_3d;id;is_service;persistent;service_accept_passive_checks;service_acknowledged;service_acknowledgement_type;service_action_url;service_action_url_expanded;service_active_checks_enabled;service_check_command;service_check_interval;service_check_options;service_check_period;service_check_type;service_checks_enabled;service_comments;service_comments_with_info;service_contact_groups;service_contacts;service_current_attempt;service_current_notification_number;service_custom_variable_names;service_custom_variable_values;service_custom_variables;service_description;service_display_name;service_downtimes;service_downtimes_with_info;service_event_handler;service_event_handler_enabled;service_execution_time;service_first_notification_delay;service_flap_detection_enabled;service_groups;service_has_been_checked;service_high_flap_threshold;service_icon_image;service_icon_image_alt;service_icon_image_expanded;service_in_check_period;service_in_notification_period;service_initial_state;service_is_executing;service_is_flapping;service_last_check;service_last_hard_state;service_last_hard_state_change;service_last_notification;service_last_state;service_last_state_change;service_last_time_critical;service_last_time_ok;service_last_time_unknown;service_last_time_warning;service_latency;service_long_plugin_output;service_low_flap_threshold;service_max_check_attempts;service_modified_attributes;service_modified_attributes_list;service_next_check;service_next_notification;service_no_more_notifications;service_notes;service_notes_expanded;service_notes_url;service_notes_url_expanded;service_notification_interval;service_notification_period;service_notifications_enabled;service_obsess_over_service;service_percent_state_change;service_perf_data;service_plugin_output;service_pnpgraph_present;service_process_performance_data;service_retry_interval;service_scheduled_downtime_depth;service_state;service_state_type;source;type
thrukadmin;aoi;1638832532;1;0;0;1;0;1;;;1;hostname;hostname;check-host-alive;1;0;5;;24x7;0;1;;12;12|thrukadmin|aoi;serveradmins;pagerduty-sys;1;0;;;;hostname;;;0;4.59198999405;;0;1;Systems,DC1,LinuxServers,LinuxVirtualServers;;1;50;;;;1;1;;0;0;1638832771;0;1638831275;0;UP;1638831275;0;0;1638832777;1.6872959137;;25;3;0;;hostname;1638833070;0;0;;;;;120;24x7;1;5;0;0;5;0;0;5;0;0;0;0;;0;4.1;"rta=0.217000ms;3000.000000;5000.000000;0.000000 pl=0%;80;100;0";PING OK - Packet loss = 0%, RTA = 0.22 ms;0;1;1;0;sys-ssh,sys-CPU 15 Minute Average,sys-/-root Disk Usage Percentage,sys-CPU 5 Minute Average,sys-Uptime;;sys-ssh|0|1,sys-CPU 15 Minute Average|0|1,sys-/-root Disk Usage Percentage|0|1,sys-CPU 5 Minute Average|0|1,sys-Uptime|0|1;0;1;;;0;0;;;;12;0;1;1;0;1;;;1;check-host-alive;5;;24x7;0;1;12;12|thrukadmin|aoi;serveradmins;pagerduty-sys;1;0;;;;;hostname;;;;0;4.59198999405;0;1;Systems,IAD4,LinuxServers,LinuxVirtualServers;1;50;;;;1;1;;0;0;1638832771;0;1638831275;0;UP;1638831275;0;0;0;0;1.6872959137;;25;3;0;;1638833070;0;0;;;;;120;24x7;1;0;4.1;"rta=0.217000ms;3000.000000;5000.000000;0.000000 pl=0%;80;100;0";PING OK - Packet loss = 0%, RTA = 0.22 ms;0;1;1;0;0;1;1;1
After reloading shinken
shinken1:/tmp# /etc/init.d/shinken status
Checking status of scheduler
scheduler RUNNING (pid 13057)
...done.
Checking status of poller
poller RUNNING (pid 13138)
...done.
Checking status of reactionner
reactionner RUNNING (pid 13214)
...done.
Checking status of broker
broker RUNNING (pid 13344)
...done.
Checking status of receiver
receiver RUNNING (pid 13422)
...done.
Checking status of arbiter
arbiter RUNNING (pid 17660)
...done.
shinken1:/tmp# /etc/init.d/shinken reload
Reloading arbiter
Doing config check
...done.
...done.
shinken1:/tmp# /etc/init.d/shinken status
Checking status of scheduler
scheduler RUNNING (pid 13057)
...done.
Checking status of poller
poller RUNNING (pid 13138)
...done.
Checking status of reactionner
reactionner RUNNING (pid 13214)
...done.
Checking status of broker
broker RUNNING (pid 13344)
...done.
Checking status of receiver
receiver RUNNING (pid 13422)
...done.
Checking status of arbiter
arbiter RUNNING (pid 21996)
...done.
shinken1:/tmp# curl -i -X POST http://localhost:50000/query -H "Content-Type: text/xml" --data-binary "@/tmp/query"
(no result)
shinken UI has the comments even after the reload
