Allow alerting on tables with relative/indirect glues. #932

Merged
merged 3 commits into from May 7, 2015

Projects

None yet

2 participants

@f0o
Member
f0o commented May 7, 2015

This commit introduces a lookup using an adaption of left/right expansion searches to find a missing glue-column across several layers of relations.
You can now alert on data having a glue mapped to other entities as long as it resolves to 'device_id' in under 30 cycles.
First intention of usage is to alert on bill-usages.
The bills-table does not contain a valid 'device_id' glue and has to be resolved via 'bills.bill_id -> bill_ports.port_id -> ports.device_id'.
This example consumes 3+1 cycles.

NOTE: This PR is considered as a fairly big update to the way rules are interpreted. Please test thoroughly and in-depth (yes I know this is redundant but really now ;)

Related: #931

@f0o f0o Allow alerting on tables with relative/indirect glues.
This commit introduces a lookup using an adaption of left/right expansion searches to find a missing glue-column across several layers of relations.
You can now alert on data having a glue mapped to other entities as long as it resolves to 'device_id' in under 30 cycles.
First intention of usage is to alert on bill-usages.
The bills-table does not contain a valid 'device_id' glue and has to be resolved via 'bills.bill_id -> bill_ports.port_id -> ports.device_id'.
This example consumes 3+1 cycles.
fadaffa
@laf laf self-assigned this May 7, 2015
@laf laf added the enhancement label May 7, 2015
f0o added some commits May 7, 2015
@f0o f0o Fix silly SQL bug 740e85a
@f0o f0o Make scrut happy 6ab9b97
@laf laf merged commit 48ea557 into librenms:master May 7, 2015

1 check passed

Scrutinizer No new issues
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment