diff --git a/docs/storage.md b/docs/storage.md index d177b2bc01..d14bc02000 100644 --- a/docs/storage.md +++ b/docs/storage.md @@ -14,14 +14,14 @@ In order to run these services, core services, as well as the network from the c Writers provide an implementation of various `message writers`. Message writers are services that consume Mainflux messages, transform them to `SenML` format, and store them in specific data store. -Each writer can filter messages based on subjects list that is set in `subjects.toml` configuration file. If you want to listen on all subjects, just pass one element ["channel.>"], otherwise pass the list of subjects. Here is an example: +Each writer can filter messages based on subjects list that is set in `subjects.toml` configuration file. If you want to listen on all subjects, just pass one element ["channels.>"], otherwise pass the list of subjects. Here is an example: ```toml [subjects] -filter = ["channel.>"] +filter = ["channels.>"] ``` -Regarding the [Subtopics Section](messaging.md#subtopics) in the messaging page, the example `channels//messages/bedroom/temperature` can be filtered as `"channel.*.bedroom.temperature"`. The formatting of this filtering list is determined by the NATS format ([Subject-Based Messaging](https://docs.nats.io/nats-concepts/subjects) & [Wildcards](https://docs.nats.io/nats-concepts/subjects#wildcards)). +Regarding the [Subtopics Section](messaging.md#subtopics) in the messaging page, the example `channels//messages/bedroom/temperature` can be filtered as `"channels.*.bedroom.temperature"`. The formatting of this filtering list is determined by the NATS format ([Subject-Based Messaging](https://docs.nats.io/nats-concepts/subjects) & [Wildcards](https://docs.nats.io/nats-concepts/subjects#wildcards)). ### InfluxDB, InfluxDB-writer and Grafana