Alert template recovery: how to get actual value instead of alerted one

[patux]

Hi,

I’m working on alert templates using Telegram transport.

We notify admins when a BGP session goes down, a filesystem reach more than certain mark, etc. We make a list by iterating faults to give more information to sysadmin

A filesystem was at 92% of usage when alert was triggered. Then when the problem was resolved, the filesystem was at 65%, but the recovery message still say 92%. I would like to notify admin team, that the problem was resolved and the filesystem is now at 65%. I thing that this can’t be possible just iterating the faults list.

Is there a way to do this? Or may be a feature request?

Thanks in advance.

[murrant]

Probably not the best idea but you could.

{{ \App\Models\Storage::find($value['storage_id'])->storage_perc }}

No guarantees that won’t break your alerting

[patux]

@murrant

ld.

{{ \App\Models\Storage::find($value['storage_id'])->storage_perc }}

I did a first test and it works.
Thanks!

Looks intresting that we can use Librenms classes on alert templating

[patux]

Here is the final alert template:

{{ $alert->title }}
` Host     : {{ $alert->hostname }}`
` sysName  : {{ $alert->sysName }}`
` Time     : {{ $alert->timestamp }}`
` State    : @if ($alert->state == 0)Ok @endif @if ($alert->state == 1)✋ Warning @endif`
` Rule     : @if ($alert->name){{ $alert->name }} @else {{ $alert->rule }} @endif `
` Unique-ID: {{ $alert->uid }}`
@if ($alert->state == 0) ⏳ Time elapsed:  {{ $alert->elapsed }} @endif 
@if ($alert->faults) 
Filesystems:
@foreach ($alert->faults as $key => $value)
`   ⭗ {{ $value['storage_descr'] }}: ({{ \App\Models\Storage::find($value['storage_id'])->storage_perc }}%)`
@endforeach 
@endif 
@if ($alert->alert_notes)
✍ *Notes:* 
{{$alert->alert_notes}}
@endif
https://mynet/device/device={{ $alert->hostname }}/tab=alerts/

[murrant]

You could put the old value in there too

[TheGreatDoc]

Dude, your template looks awesome.

I use telegram too. Do you mind sharing them?

[murrant]

My url goes to /tab=health/metric=storage/

[tamatsuna]

I would like to get the actual value of port utilization.
It seems to be able to get with the following code. It’s OK?

Input : {{ \App\Models\Port::find($value['port_id'])->ifInOctets_rate *8 / $value['ifSpeed'] *100 }} %
Output: {{ \App\Models\Port::find($value['port_id'])->ifOutOctets_rate *8 / $value['ifSpeed'] *100 }} %

[DBMandrake]

@murrant

Probably not the best idea but you could.

{{ \App\Models\Storage::find($value['storage_id'])->storage_perc }}

No guarantees that won’t break your alerting

@tamatsuna

I would like to get the actual value of port utilization.
It seems to be able to get with the following code. It’s OK?

Input : {{ \App\Models\Port::find($value['port_id'])->ifInOctets_rate *8 / $value['ifSpeed'] *100 }} %
Output: {{ \App\Models\Port::find($value['port_id'])->ifOutOctets_rate *8 / $value['ifSpeed'] *100 }} %

Thanks to both of you for these. I’ve updated my templates for high port usage and low disk space using the above to grab the most up to date figures during the recovery alert, and it’s a lot more useful IMHO to see what the port traffic or disk space use actually is after the alerting condition has passed reported by the recovery alert.

One thing I did notice before doing this though is that the figures in $value for recovery alerts were not the original values recorded when the alert first triggered - they are the values recorded in the previous polling period. So if the alert persists for multiple 5 minute polling periods the recovery alert shows values from the previous poll that occurred after the original alert but before the alert condition was resolved.

So the recovery values were often different from the initial alert if the alert lasted more than one polling period and the quantity being measured was varying, but they were still values within the alerting range rather than values outside the alerting range that will be shown now with direct access to the most up to date data.