Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

need more details on lsc.status like task and phase #90

Closed
gallak opened this issue Sep 13, 2019 · 3 comments
Closed

need more details on lsc.status like task and phase #90

gallak opened this issue Sep 13, 2019 · 3 comments
Assignees
Milestone

Comments

@gallak
Copy link

gallak commented Sep 13, 2019

I think that lsc.status loose some informations because is shows only summary of modified entries or errors.

It should be useful to have more details like
number of entries, modified entries, deleted entries per task and phase

I suggest this kind of output :

sept. 12 12:10:50 - INFO  - All entries: 197, to modify entries: 0, successfully modified entries: 0, errors: 0 - task : sync A-firstTask 
sept. 12 12:10:50 - INFO  - All entries: 197, to modify entries: 1, successfully deleted entries: 1, errors: 0 - task : clean A-firstTask 
sept. 12 12:10:50 - INFO  - All entries: 150, to modify entries: 4, successfully modified entries: 3, errors: 1 - task : sync B-secondTask 

as a consequence , nagios script should modified with the following syntax :
check_lsc_status_file.pl -l /path/of/file -t -syncw -syncc -cleanw -cleanc -f ...

for example
2 task like A-firstTask with sync and clean phase and B-secondTask with only sync phase

check_lsc_status_file.pl \
-l /var/log/lsc/lsc.status \
-t A-firstTask \
-syncw 0 \
-syncc 0 \
-cleanw 0 \
-cleanc 0 \
-t B-secondTask \
-syncw 0 \
-syncc 0 \
-f  ... 

Task name should be followed at least by 2 values of critical and warning level for sync or clean phase.

The response could be :
WARN - LSC is running with some errors (A-FirstTask, SW=0,SC=0,CS=0,CC=0/ B-SecondTask, SW=0,SC=0|'A_FirstTask__all'=197 'A_FirstTask__SW'=0 'A_FirstTask__SC'=0 'A_FirstTask__CW'=0 'A_FirstTask__CC'=0;0;0 |'B_SecondTask__all'=150 'B_SecondTask__SW'=0 'B_SecondTask__SC'=0 ;1

@gallak
Copy link
Author

gallak commented Sep 13, 2019

as suggest by mail : #53 (comment)
It do the same job but it is more expensive ( one reading versus one reading per phase per task)

@coudot coudot self-assigned this Feb 10, 2020
@coudot coudot added this to the 2.2 milestone Feb 10, 2020
@coudot
Copy link
Member

coudot commented Jul 15, 2021

This will be done with #53

@coudot coudot closed this as completed Jul 15, 2021
@coudot
Copy link
Member

coudot commented Aug 27, 2024

See #302

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants