stork issueshttps://gitlab.isc.org/isc-projects/stork/-/issues2022-12-05T10:00:11Zhttps://gitlab.isc.org/isc-projects/stork/-/issues/839stork-agent: Encountered unsupported stat2022-12-05T10:00:11ZMunroe Sollogstork-agent: Encountered unsupported stat---
name: Bug report
about: stork-agent Encountered unsupported stat
---
**Describe the bug**
When enabling prometheus output I get errors in the log and no data in grafana:
```
Aug 16 10:43:39 rover stork-agent[56760]: time="2022-08-1...---
name: Bug report
about: stork-agent Encountered unsupported stat
---
**Describe the bug**
When enabling prometheus output I get errors in the log and no data in grafana:
```
Aug 16 10:43:39 rover stork-agent[56760]: time="2022-08-16 10:43:39" level="info" msg="Encountered unsupported stat: cumulative-assigned-addresses" file=" promkeaexporter.go:683 "
Aug 16 10:43:39 rover stork-agent[56760]: time="2022-08-16 10:43:39" level="info" msg="Encountered unsupported stat: reclaimed-declined-addresses" file=" promkeaexporter.go:683 "
Aug 16 10:43:39 rover stork-agent[56760]: time="2022-08-16 10:43:39" level="info" msg="Encountered unsupported stat: declined-addresses" file=" promkeaexporter.go:683 "
Aug 16 10:43:39 rover stork-agent[56760]: time="2022-08-16 10:43:39" level="info" msg="Encountered unsupported stat: reclaimed-leases" file=" promkeaexporter.go:683 "
```
**To Reproduce**
Steps to reproduce the behavior:
Stork 1.5.0 with config:
```
STORK_AGENT_LISTEN_PROMETHEUS_ONLY=true
STORK_AGENT_PROMETHEUS_KEA_EXPORTER_ADDRESS= 127.0.0.1
STORK_AGENT_PROMETHEUS_KEA_EXPORTER_INTERVAL= 60
STORK_AGENT_PROMETHEUS_KEA_EXPORTER_PER_SUBNET_STATS=true
STORK_AGENT_SKIP_TLS_CERT_VERIFICATION=true
```
**Expected behavior**
Data should be be properly scraped from the kea api and exposed via prometheus.
**Environment:**
Kea version info:
```
# kea-dhcp4 -V
2.0.1
tarball
linked with:
log4cplus 1.1.2
OpenSSL 1.1.1n 15 Mar 2022
database:
MySQL backend 12.0, library 10.3.34
PostgreSQL backend 6.2, library 110016
Memfile backend 2.1
```
Using the following hooks:
```
"hooks-libraries": [
{
"library": "/usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_lease_cmds.so",
"parameters": { }
},
{
"library": "/usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_stat_cmds.so",
"parameters": { }
},
{
"library": "/usr/lib/x86_64-linux-gnu/kea/hooks/libdhcp_ha.so",
"parameters": {
"high-availability": [
{
"this-server-name": "rover",
"mode": "hot-standby",
"heartbeat-delay": 2000,
"max-response-delay": 12000,
"max-ack-delay": 10000,
"max-unacked-clients": 0,
"multi-threading": {
"enable-multi-threading": true,
"http-dedicated-listener": true,
},
"peers": [
{
"name": "rover",
"role": "primary",
"auto-failover": true
}, {
"name": "spot",
"role": "standby",
"auto-failover": true
}
]
}
]
}
}
]
```1.8Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/issues/576alerting: server should report statistics to Prometheus2021-11-04T10:18:55ZTomek Mrugalskialerting: server should report statistics to PrometheusImplement the ability in Stork server to export statistics to Prometheus. For the time being I think the following stats should be made available:
1. number of authorized machines
2. number of unauthorized machines
3. number of unreacha...Implement the ability in Stork server to export statistics to Prometheus. For the time being I think the following stats should be made available:
1. number of authorized machines
2. number of unauthorized machines
3. number of unreachable machines
The third statistic should report 0 under normal circumstances, so not exactly exciting. The idea is that an admin could set up an alarm for non-zero value reported. For the first two, a careful admin may set up an alert if there's a new machine in the system, e.g. when someone tries to set up a fake machine or when the system is scaled up by adding new VM with Kea.
In the future we may also report the number of error events or something similar. The general idea here is to offload the alterting to prometheus. We were supposed to provide some alterting mechanisms, but instead of implementing them ourselves in Stork, it's much more robust to use existing mechanisms from Prometheus.0.22Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/issues/574No information about the network in the prometheus exporter stork agent2021-11-03T13:46:34ZOleg ZeibelNo information about the network in the prometheus exporter stork agent---
name: Feature request
about: In the prometheus exporter of the agent, you need to show information about the network
---
**Some initial questions**
- Are you sure what you would like to do is not possible using some other mechanisms...---
name: Feature request
about: In the prometheus exporter of the agent, you need to show information about the network
---
**Some initial questions**
- Are you sure what you would like to do is not possible using some other mechanisms?
I have not found how to do it differently
- Stork is in very early stages of development. If your request is not simple, it
may be a while until anyone does anything with your request. Are you ok with that?
Yes
**Is your feature request related to a problem? Please describe.**
Stork prometheus exporter does not provide any information about the DHCP network. Network ID only.
This id has a numerical value and in the graphana dashboard this indicator is not at all visual.
**Describe the solution you'd like**
I would like to see information about the network. For example, in this form
kea_dhcp4_addresses_assigned_total{subnet="10.10.10.0/24"} 3
kea_dhcp4_addresses_declined_reclaimed_total{subnet="10.10.10.0/24"} 0
and other
**Describe alternatives you've considered**
Now we are trying to display the network through the grafana dashboard and the selection of the network ID
**Contacting you**
e-mail: iceadler@gmail.com / o.zejbel@robo.finance0.22Slawek FigielSlawek Figielhttps://gitlab.isc.org/isc-projects/stork/-/issues/231Links to Grafana2020-04-16T19:55:33ZTomek MrugalskiLinks to GrafanaWe need a better intergration with Grafana. For the time being we could add the following:
- [x] ~~ability to open Grafana in iframe. This is lightweight and would look as visually integrated solution. (I've attached a mockup of how thi...We need a better intergration with Grafana. For the time being we could add the following:
- [x] ~~ability to open Grafana in iframe. This is lightweight and would look as visually integrated solution. (I've attached a mockup of how this could look like).~~ @godfryd tried this and it was infeasible due to XSS protections. WE opted to go with dedicated links on stork pages.
- [ ] for the demo in April, the link could be hardcoded
- [x] for the 0.7 release, we could have the Grafana (and Prometheus) links configurable in the db.0.7Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/stork/-/issues/167integrate stork with prometheus2020-03-02T13:46:24ZMichal Nowikowskiintegrate stork with prometheus0.5Michal NowikowskiMichal Nowikowski