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

SLA Business Report - availilibity accuracy #1416

Open
jframeau opened this issue Dec 17, 2024 · 1 comment
Open

SLA Business Report - availilibity accuracy #1416

jframeau opened this issue Dec 17, 2024 · 1 comment

Comments

@jframeau
Copy link
Contributor

More of a thought than a bug.

Let's say we have a bp like this: Worst -> BP A -> BP B

BP A sees these events (only hard criticals are take into account):

4 criticals

[2024-11-15 03:12:54] SERVICE ALERT: B;B;OK;HARD;3;OK
[2024-11-15 03:12:03] SERVICE ALERT: B;B;CRITICAL;HARD;3
[2024-11-15 03:10:39] SERVICE ALERT: B;B;OK;HARD;3
[2024-11-15 03:10:03] SERVICE ALERT: B;B;CRITICAL;HARD;3
[2024-11-15 03:08:07] SERVICE ALERT: B;B;OK;HARD;3
[2024-11-15 03:07:03] SERVICE ALERT: B;B;CRITICAL;HARD;3
[2024-11-15 02:10:03] SERVICE ALERT: B;B;OK;HARD;3
[2024-11-15 02:07:03] SERVICE ALERT: B;B;CRITICAL;HARD;3

So are outages for B:

Start End Duration Type Plugin Output
2024-11-15 03:12:03 2024-11-15 03:12:54 0d 0h 0m 51s SERVICE CRITICAL (HARD) ...
2024-11-15 03:10:03 2024-11-15 03:10:39 0d 0h 0m 36s SERVICE CRITICAL (HARD) ...
2024-11-15 03:07:03 2024-11-15 03:08:07 0d 0h 1m 4s SERVICE CRITICAL (HARD) ...
2024-11-15 02:07:03 2024-11-15 02:09:03 0d 0h 2m 0s SERVICE CRITICAL (HARD) ...

sum = 4 mn 31s

Now for A:

3 criticals

[2024-11-15 03:10:13] SERVICE ALERT: A;A;OK;HARD;3
[2024-11-15 03:10:03] SERVICE ALERT: A;A;CRITICAL;HARD;3
[2024-11-15 03:08:20] SERVICE ALERT: A;A;OK;HARD;3
[2024-11-15 03:08:03] SERVICE ALERT: A;A;CRITICAL;HARD;3
[2024-11-15 03:06:17] SERVICE ALERT: A;A;OK;HARD;3
[2024-11-15 02:11:03] SERVICE ALERT: A;A;OK;HARD;3
[2024-11-15 02:08:03] SERVICE ALERT: A;A;CRITICAL;HARD;3

Si are outages for A

Start End Duration Type Plugin Output
2024-11-15 03:10:03 2024-11-15 03:10:13 0d 0h 0m 10s SERVICE CRITICAL (HARD) ...
2024-11-15 03:08:03 2024-11-15 03:08:20 0d 0h 0m 17s SERVICE CRITICAL (HARD) ...
2024-11-15 02:08:03 2024-11-15 02:10:03 0d 0h 2m 0s SERVICE CRITICAL (HARD) ...

sum = 2 mn 27s

Big difference !

I think it's inherent in the way we calculate so there's a loss of precision from bottom to top of the bp.

If I understand correctly, bp statuses are computed from command thruk bp all in crontab and cron is just 1 mn accurate.

I wonder if it's possible to shorten the time between two calculations?

jfr

@sni
Copy link
Owner

sni commented Dec 17, 2024

The default is 1 minute, but you can run the BP calculations as often as you like.

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

No branches or pull requests

2 participants