summary | shortlog | log | commit | commitdiff | tree
raw | patch | inline | side by side (parent: ccf53ee)
raw | patch | inline | side by side (parent: ccf53ee)
author | Sebastian Harl <sh@tokkee.org> | |
Mon, 16 Jun 2008 21:35:28 +0000 (23:35 +0200) | ||
committer | Florian Forster <octo@huhu.verplant.org> | |
Tue, 17 Jun 2008 19:53:54 +0000 (21:53 +0200) |
As suggested by Wolfgang Kroener.
Signed-off-by: Sebastian Harl <sh@tokkee.org>
Signed-off-by: Florian Forster <octo@huhu.verplant.org>
Signed-off-by: Sebastian Harl <sh@tokkee.org>
Signed-off-by: Florian Forster <octo@huhu.verplant.org>
contrib/examples/MyPlugin.pm | patch | blob | history | |
contrib/examples/myplugin.c | patch | blob | history |
index 1a0247ff8e068cb7c1fd0d5b30169413f9977635..13806ee91157fc1592b220b5191b192907ab264c 100644 (file)
# data set definition:
# see section "DATA TYPES" in collectd-perl(5) for details
-# (take a look at the types.db file for a large list of predefined data-sets)
+#
+# NOTE: If you're defining a custom data-set, you have to make that known to
+# any servers as well. Else, the server is not able to store values using the
+# type defined by that data-set.
+# It is strongly recommended to use one of the types and data-sets pre-defined
+# in the types.db file.
my $dataset =
[
{
# dispatch the values to collectd which passes them on to all registered
# write functions - the first argument is used to lookup the data set
- # definition
+ # definition (it is strongly recommended to use a type defined in the
+ # types.db file)
plugin_dispatch_values ('myplugin', $vl);
# A false return value indicates an error and the plugin will be skipped
index cdd537a755327e94959a2808750f665a84d1bdc8..240c6c3a8932cd0f8c31e485edf202ca96e93d38 100644 (file)
* - name of the data set
* - number of data sources
* - list of data sources
+ *
+ * NOTE: If you're defining a custom data-set, you have to make that known to
+ * any servers as well. Else, the server is not able to store values using the
+ * type defined by that data-set.
+ * It is strongly recommended to use one of the types and data-sets
+ * pre-defined in the types.db file.
*/
static data_set_t ds =
{
/* dispatch the values to collectd which passes them on to all registered
* write functions - the first argument is used to lookup the data set
- * definition */
+ * definition (it is strongly recommended to use a type defined in the
+ * types.db file) */
plugin_dispatch_values ("myplugin", &vl);
/* A return value != 0 indicates an error and the plugin will be skipped