Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
F
FFS Gluon
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Container registry
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
0x4A6F
FFS Gluon
Commits
4d6956fa
Commit
4d6956fa
authored
9 years ago
by
Matthias Schiffer
Browse files
Options
Downloads
Patches
Plain Diff
docs: update outdated monitoring documentation
parent
10d7ad21
No related branches found
No related tags found
No related merge requests found
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
docs/features/monitoring.rst
+38
-63
38 additions, 63 deletions
docs/features/monitoring.rst
docs/index.rst
+1
-1
1 addition, 1 deletion
docs/index.rst
with
39 additions
and
64 deletions
docs/features/
announce
.rst
→
docs/features/
monitoring
.rst
+
38
−
63
View file @
4d6956fa
Announcing Node Information
Node monitoring
===============
============
===============
Gluon is capable of announcing information about each node to the mesh
Gluon is capable of announcing information about each node to the mesh
and to neighbouring nodes. This allows nodes to learn each others hostname,
and to neighbouring nodes. This allows nodes to learn each others hostname,
...
@@ -8,7 +8,7 @@ IP addresses, location, software versions and various other information.
...
@@ -8,7 +8,7 @@ IP addresses, location, software versions and various other information.
Format of collected data
Format of collected data
------------------------
------------------------
Information to be announced is currently split into t
wo
categories:
Information to be announced is currently split into t
hree
categories:
nodeinfo
nodeinfo
In this category (mostly) static information is collected. If
In this category (mostly) static information is collected. If
...
@@ -19,8 +19,12 @@ Information to be announced is currently split into two categories:
...
@@ -19,8 +19,12 @@ Information to be announced is currently split into two categories:
This category holds fast changing data, like traffic counters, uptime,
This category holds fast changing data, like traffic counters, uptime,
system load or the selected gateway.
system load or the selected gateway.
Both categories will have a ``node_id`` key by default. It should be used to
neighbours
match data from *statistics* to *nodeinfo*.
`neighbours` contains information about all neighbouring nodes of all
interfaces. This data can be used to determine the network topology.
All categories will have a ``node_id`` key. It should be used to
relate data of different catagories.
Accessing Node Information
Accessing Node Information
--------------------------
--------------------------
...
@@ -43,8 +47,13 @@ installed. Please note that at least one alfred daemon is required to run as
...
@@ -43,8 +47,13 @@ installed. Please note that at least one alfred daemon is required to run as
.. _alfred-json: https://github.com/tcatm/alfred-json
.. _alfred-json: https://github.com/tcatm/alfred-json
`nodeinfo` is distributed as alfred datatype `158`, while `statistics` uses
The following datatypes are used:
`159`. Both are compressed using GZip (alfred-json can handle the decompression).
* `nodeinfo`: 158
* `statistics`: 159
* `neighbours`: 160
All data is compressed using GZip (alfred-json can handle the decompression).
In order to retrieve statistics data you could run:
In order to retrieve statistics data you could run:
...
@@ -90,18 +99,26 @@ You can find more information about alfred in its README_.
...
@@ -90,18 +99,26 @@ You can find more information about alfred in its README_.
.. _README: http://www.open-mesh.org/projects/alfred/repository/revisions/master/entry/README
.. _README: http://www.open-mesh.org/projects/alfred/repository/revisions/master/entry/README
gluon-
announce
d
gluon-
respond
d
~~~~~~~~~~~~~~
~
~~~~~~~~~~~~~~
`gluon-
announce
d` allows querying neighbouring nodes for their
`nodeinfo`
.
`gluon-
respond
d` allows querying neighbouring nodes for their
information
.
It is a daemon listening on the multicast address ``ff02::2:1001`` on
It is a daemon listening on the multicast address ``ff02::2:1001`` on
UDP port 1001 on the bare mesh interfaces.
UDP port 1001 on both the bare mesh interfaces and `br-client`. Unicast
requests are supported as well.
The supported requests are:
* ``nodeinfo``, ``statistics``, ``neighbours``: Returns the data of single category uncompressed.
* ``GET nodeinfo``, ...: Returns the data of one or multiple categories (separated by spaces)
compressed using the `deflate` algorithm (without a gzip header). The data may
be decompressed using zlib and many zlib bindings using -15 as the window size parameter.
gluon-neighbour-info
gluon-neighbour-info
~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~
A
programm
called
`gluon-neighbour-info`
has been develop
ed to retrieve
The
programm `gluon-neighbour-info`
can be us
ed to retrieve
information from
neighbour
s.
information from
other node
s.
::
::
...
@@ -109,55 +126,13 @@ information from neighbours.
...
@@ -109,55 +126,13 @@ information from neighbours.
-p 1001 -d ff02:0:0:0:0:0:2:1001 \
-p 1001 -d ff02:0:0:0:0:0:2:1001 \
-r nodeinfo
-r nodeinfo
On optional timeout may be specified, e.g. `-t 5` (default: 3 seconds).
An optional timeout may be specified, e.g. `-t 5` (default: 3 seconds). See
the usage information printed by ``gluon-neighbour-info -h`` for more information
Adding a fact
about the supported arguments.
-------------
To add a fact just add a file to either ``/lib/gluon/announce/nodeinfo.d/`` o
r
Adding a data provide
r
``/lib/gluon/announce/statistics.d/``.
----------------------
The file must contain a lua script and its name will become the key for the
To add a provider, you need to install a shared object into ``/lib/gluon/respondd``.
resulting JSON object. A simple script adding a ``hostname`` field might look
For more information, refer to the `respondd README <https://github.com/freifunk-gluon/packages/blob/master/net/respondd/README.md>`_
like this:
and have a look the existing providers.
::
return uci:get_first('system', 'system', 'hostname')
The directory structure will be converted to a JSON object, i.e. you may
create subdirectories. So, if the directories look like this
::
.
├── hardware
│ └── model
├── hostname
├── network
│ └── mac
├── node_id
└── software
└── firmware
the resulting JSON would become:
::
# /lib/gluon/announce/announce.lua nodeinfo
{
"hardware" : {
"model" : "TP-Link TL-MR3420 v1"
},
"hostname" : "mr3420-test",
"network" : {
"mac" : "90:f6:52:82:06:02"
},
"node_id" : "90f652820602",
"software" : {
"firmware" : {
"base" : "gluon-v2014.2-32-ge831099",
"release" : "0.4.1+0-exp20140720"
}
}
}
This diff is collapsed.
Click to expand it.
docs/index.rst
+
1
−
1
View file @
4d6956fa
...
@@ -27,7 +27,7 @@ Features
...
@@ -27,7 +27,7 @@ Features
features/wlan-configuration
features/wlan-configuration
features/private-wlan
features/private-wlan
features/wired-mesh
features/wired-mesh
features/
announce
features/
monitoring
features/authorized-keys
features/authorized-keys
features/roles
features/roles
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment