Netdata is not working with MySQL, only MariaDB. This is because this command SHOW USER_STATISTICS in this file only works in MariaDB.

Problem code is https://github.com/netdata/netdata/blob/bfae683664b488df91940a81760459db2b18983c/collectors/python.d.plugin/mysql/mysql.chart.py

My install is http://walkercodetutorials.codes:19999

With log: {backend: "stdout", level: "..."} in config.js the daemon ignores the log level and still prints everything to stdout. This seems to be the result of lib/logger.js using util.log (deprecated since 6.0.0 20 months ago) which does not support log levels.

If the stdout logger cannot be easily made to respect the log level, it would be helpful if the config documentation in `exam

In statsd's documentation, they note that when not updated, a gauge will flush it's previous value (https://github.com/etsy/statsd/blob/master/docs/metric_types.md#gauges).

Does this behavior exist in statsite? Or will values only be flushed if they've been received within the flush period?

It would be great if the amon agent can monitor ZFS and BTRFS pools and if it could also monitor the state of such pools.

http://docs.grafana.org/installation/debian/#apt-repository
The Dockerfile doesn't contain creating a file /etc/apt/sources.list.d/grafana.list.
The Latest version of the Dockerfile installs Grafana 2.6.0, and latest Grafana version is 6.x.
It would be great to support newer versions 👍

curl https://baidu.com -I
HTTP/1.1 302 Moved Temporarily
Server: bfe/1.0.8.18
Date: Thu, 20 Dec 2018 06:41:40 GMT
Content-Type: text/html
Content-Length: 161
Connection: keep-alive
Location: http://www.baidu.com/

The graphite source by default will listen on TCP, port 2004 for plaintext protocol. Apparently, this should be 2003, not 2004 which is the pickle port. This change should be simple to do but it will be backward incompatible, so it'll need to be lined up with 0.8.0 or some other major release.

This would allow for internal metrics to be monitored from prom.

This could be useful when there's a large number of ephemeral hosts, and other backends may not scale as well with the high cardinality of internal metrics across many hosts.

This is mostly stand-alone and doesn't interact with the more complicated aspects of how gostatsd handles things, as it's mostly just adding an http serve

Do you think we can extend the library to include events and service-checks reporting?

https://docs.datadoghq.com/guides/dogstatsd/#events
https://docs.datadoghq.com/guides/dogstatsd/#service-checks

If you think we can go in that direction I will open a PR.

Tags are a slice of strings in the documentation, but datadog-go documentation does not mention valid values for tags. datadog-go removes newlines from tags, but does not remove/escape other invalid characters like comma (,). Comma in tag value will be interpreted as multiple tags since tags are comma-separated in the UDP datagrams.

The page at https://docs.datadoghq.com/developers/guide/wh

See http://docs.datadoghq.com/guides/dogstatsd/

In particular they have histograms (key |h), allows sampling all inputs and has support for key/value tagging (|#key:value;key2).

If we want to broaden the scope a bit, events and service-checks could be supported too.

As you can see with the link below, in documentation sampleRate is explained as percentage which causes some users to use values between 0-100 but expected value is actually between 0-1. Could you please update the documentation to sth like:

sampleRate:
 rate of the sampling (expected value between 0.0 and 1.0)

https://github.com/DataDog/java-dogstatsd-client/blob/2c972e6f011e6524

Configure Grafana locally to integrate with Prometheus so that we can use it locally