From fe9a686e8319c56bb42ef72fdd0f01eeee5e0f92 Mon Sep 17 00:00:00 2001 From: f0o Date: Sat, 26 Sep 2015 18:25:22 +0000 Subject: [PATCH] Updated docs --- doc/Extensions/Alerting.md | 2 +- doc/Extensions/Device-Groups.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/Extensions/Alerting.md b/doc/Extensions/Alerting.md index 92d264e203..bd0b1a7860 100644 --- a/doc/Extensions/Alerting.md +++ b/doc/Extensions/Alerting.md @@ -66,7 +66,7 @@ __Conditions__ can be any of: __Values__ can be Entities or any single-quoted data. __Glues__ can be either `&&` for `AND` or `||` for `OR`. -__Note__: The difference between `Equals` and `Matches` (and it's negation) is that `Equals` does a strict comparison and `Matches` allows the usage of the placeholder `@`. The placeholder `@` is comparable with `.*` in RegExp. +__Note__: The difference between `Equals` and `Matches` (and it's negation) is that `Equals` does a strict comparison and `Matches` allows the usage of RegExp. Arithmetics are allowed as well. ## Examples diff --git a/doc/Extensions/Device-Groups.md b/doc/Extensions/Device-Groups.md index cc48cdaad7..c38db06a89 100644 --- a/doc/Extensions/Device-Groups.md +++ b/doc/Extensions/Device-Groups.md @@ -8,12 +8,12 @@ Patterns work in the same was as Entities within the alerting system, the format as __tablename.columnname__. If you are ensure of what the entity is you want then have a browse around inside MySQL using `show tables` and `desc `. As a working example and a common question, let's assume you want to group devices by hostname. If you hostname format is dcX.[devicetype].example.com. You would use the pattern -devices.hostname. Select the condition which in this case would Like and then enter dc1.@.example.com. This would then match dc1.sw01.example.com, dc1.rtr01.example.com but not +devices.hostname. Select the condition which in this case would Like and then enter `dc1\..*\.example.com`. This would then match dc1.sw01.example.com, dc1.rtr01.example.com but not dc2.sw01.example.com. #### Wildcards -As used in the example above, wildcards are represented by the @ symbol. I.e @.example.com would match any hostnames under example.com. +As with alerts, the `Like` operation allows RegExp. A list of common entities is maintained in our [Alerting docs](http://docs.librenms.org/Extensions/Alerting/#entities).