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

Proposal

**Use case. Why is

Move all Dockerfile samples to non-root user

Expected Behaviour

As an OpenFaaS end-user, I want to run all samples on my OpenFaaS cluster, even with the new non-root feature enabled.

Current Behaviour

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

Thanks to @miekg and code they added here: https://github.com/coredns/coredns/blob/master/test/metric_naming_test.go

This is a reminder for me or a task if anyone wants :P

Basically, The last two questions aren't really regex's questions.

To do:

• Move said questions to correct place.
• Add new regex questions (Python related!)?
• Maybe add a new ## Regex section, as it is a valuable skill

Host operating system: output of uname -a

Linux foo1.example.com 4.19.67 #1 SMP Thu Aug 22 16:06:16 EDT 2019 x86_64 GNU/Linux

node_exporter version: output of node_exporter --version

node_exporter, version 0.18.1 (branch: release-0.18, revision: 0037b4808adeaa041eb5dd699f7427714ca8b8c0)
build user: foo
build date: 20191030-22:24:38
go version: go1.13.3

Please help me to check this error, thank you!

Below is the description of my pod

[root@k8s-master-1 alertmanager]# kubectl describe pod prometheus-prometheus-operator-158278-prometheus-0
Name: prometheus-prometheus-operator-158278-prometheus-0
Namespace: default
Priority: 0
Node: k8s-node-2/172.29.1.102
Start Time: Mon, 02 Mar 2020 16:30:42 +0800
Labels:

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

Update M3DB intro limitations to include complex types and out of order writes support.

We have an easy way to add snappy compression to caches, and we do it for the index-read-cache. But we should add it to other caches, specially the frontend-results cache.

We had it in the frontend-cache, but we lost it in this refactoring by

Describe the bug
vmagent with sd_k8s

To Reproduce
Start vmagent with config:

    - job_name: 'kubernetes-pods'
      kubernetes_sd_configs:
      - role: pod

on a cluster with many pods.

Please add pod name to error log.

It's hard to find them in a big cluster. In a message like this it's not clear what was the pod.

2020-04-15T22:32:32.512Z	error	Victor

This is a FEATURE REQUEST.

Please add support for kube_state_metrics_build_info as part of the metrics exposed on telemetry port 8081.
kube_state_metrics_build_info shall include the version of the kube-state-metrics.
Most Prometheus exporters are currently supporting such metric.

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

What version of OpenCensus are you using?

HEAD of this repo

What version of Go are you using?

go version go1.13.4 darwin/amd64

Details

examples.PrintExporter seems to require being passed to view.RegisterExporter, but examples.LogExporter can't be passed there because it doesn't implement the write Exporter type. Instead, you're expected to run the Start metho

What happened?

The default Prometheus ClusteRole in kube-prometheus is missing some permissions compared to the Prometheus ClusterRole from documentation from the do

The documentation for this library is incomplete. It could really use some thorough API documentation. For example, what is a Registry? When does the collect method get called, and what is its contract?

It would be awesome if the metrics could include the node's topology.kubernetes.io/region & topology.kubernetes.io/zone (not sure what the non-AWS fields are called). That would help quickly identify patterns in the results. e.g., zone "a" is slower than zone "b" or that cross-zone traffic is what's causing a large spike in response times. Not sure if this is possible within the framework of this

What did you expect to see?

I'm expecting to be able to filter out the requests from blackbox exporter in my access logs.
So, please, add a user agent header that container the "blackbox exporter" string somewhere.

What did you see instead?

I see User-Agent: Go-http-client/1.1
Not easy to filter in the access logs...

Add some sort of URL (www.https://[host]:[port]/health ) in JMX exporter to return 200 which indicate that server is working fine. We had a use case where we just wanted to check the health without scrapping the beans. Idea was to check if JMX exporter service is working fine and raise alarm if JMX exporter's health is bad.
Changes can be done here:
https://github.com/prometheus/jmx_exporter/blo

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