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

Describe the bug

/usr/share/icinga2/include/command-plugins.conf provides the http CheckCommand. Since version 2.3.0 there is a new option in check_http which allows for checking the correctness of a certificate and hostname match: --verify-host. Please add this to the built in template library.

https://icinga.com/docs/icinga2/latest/doc/10-icinga-template-library/

$ /usr/

I set up grafana w/ google login, so I'm trying to use an API key to connect wizzy to the dashboards.

I see that 'grafana:api_key' is an entry in validConfigs from config.js L:21.

EDIT: Using something like

{
  "config": {
    "grafana": {
      "url": "[URL]",
      "api_key": "[KEY]"
    }
  }
}

in the wizzy.json appeared to work. Maybe it should be a documented op

The prometheus plugin uses metric names like this:

• org_graylog2_inputs_gelf_tcp_GELFTCPInput_5cc1bd20057c5200116dfdef_open_connections
• org_graylog2_lookup_adapters_5cc1bc798e510600109570d9_refresh_count
• org_graylog2_lookup_caches_5ca37df31210da0011143090_hits_total

It is really painful to write alarms for metrics like this. It would much better if the metrics would have names like th

OpenTSDB's metrics are described here:
http://opentsdb.net/docs/build/html/user_guide/stats.html

We should look specifically for metrics matching these descriptions, then set the metric type and help text accordingly.

We can also make the metric names more consistent with Prometheus' conventions:
https://prometheus.io/docs/practices/naming/