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

Steps to reproduce:

On a template variable with multi-select:

1. enter a search which matches one or more items
2. navigate by keyboard to an item
3. use space bar to toggle the item

Actual Result:
The space bar input is appended or prepended to the search text.

Expected Result
The search text should remained unchanged, since focus is on a dropdown item.

**Releva

Is your feature request related to a problem? Please describe.

We plan to do ruling and alerting like Prom with Alertmanager, but in the meantime we have multiple ways to already alerts on logs and I think we should document it.

This include alerting with Promtail/Alertmanager using stages or alerting with Grafana using Loki as Prometheus datasource.

We should also explain that you

run_begin和run_end必须要写全。03:00不能写成3:00。因为数据库中存的是字符串，比较的时候按照字符串的大小比较，3:00会小于02:00。页面应该要做校验或者提示。

参考 PR #184 的讨论

I can see that the local NodeExporter is configured to listen on port 9100 https://github.com/stefanprodan/dockprom/blob/c15864194960ec65e48dff2867d0a2f5bedb72aa/docker-compose.yml#L64

and then found the relevant config in https://github.com/stefanprodan/dockprom/blob/dbd8f15e1dc92cf46bfad6d61b4cc9cfb4ddfc45/prometheus/prometheus.yml#L19

Just to make sure that I am on the right track here an

Since kubernetes latest version has reached 1.18, in new Version we need new apiVersion value

Use 'apps/v1' to replace 'extensions/v1beta1' for example-app deployment

path : use-operator-manage-prometheus.md

current:

apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: example-app

new:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: examp

• There is no install docs detailing how to install it. the docker stuff I do not know how it is installed.
• The documentation is messy.
• There is no support docs meaning what application server you support monitoring .
• I think you have 2 parts one is the browser plugin and the other is the server , there is no clear indication between them and do I need to use both of them .

--Thank you

Is your feature request related to a problem? Please describe.
Currently 'Table' layout of Zabbix Problem panel does not handle newlines and HTML/markdown in trigger descriptions (see Screenshot 1).
I know newline is kind of a known issue, but HTML/markdown was always properly handled by the 'List' layout.

Describe the solution you'd like
Please add HTML/newline support to 'Table' l

The README.md currently mentions how to do this using DNS, but could this process not be improved on by using Consul instead?

As already mentioned in the readme, DockerSwarm.rocks recommends Traefik and HTTPS. This install uses Consul as a key-value store for the SSL certificates, which means many/most of the Docker Swarm installs following that recipe will have C

Today, we add for: 5m to alerts, automatically.

Use case: mysql_global_status_uptime < 60 would never trigger

5m can be the default value.

Progression:

Basic resource monitoring

• Prometheus self-monitoring
• Host/Hardware
• Docker Containers
• Blackbox
• Windows

Databases and brokers

• MySQL
• PostgreSQL
• PGBouncer
• [

Cloudprober supports building additional metrics (other than the default ones) from external probe output. We could possible do the same for HTTP probe.

What you expected to happen?

We should have a Links class defined for the optional dashboard links in the top right.

Current workaround is to paste the links in JSON Model format:

    return Dashboard(
        title="Grafana Metrics",
        links=[
            {
            "icon": "external link",
            "tags": [],
            "targetBlank": True,
            "titl

I don't see a CONTRIBUTING file in your repository, nor a wiki section. Do you have a vision on where you're going and would you accept pull requests?

I'm interested in adding in x86 checks to make the script viable for any architecture, specifically, x86 and CentOS.

This ticket is meant to log user feedback on current documentation insufficiencies and ideas for improvements. All ideas welcome, please add a comment if you find something illogical or missing. Thank you!

Describe the bug

Not necessary a "bug", nor a feature. More aesthetics. The color of "charging" on the pie chart is green, which reflects "sleeping" in the states dashboard.

This might be a feature :) Could we also add a pie chart to the "States" dashboard instead of the boxed legend under the continuous bar?

To Reproduce

Steps to reproduce the behavior:

1. Go to Trip da