stork issueshttps://gitlab.isc.org/isc-projects/stork/-/issues2024-03-19T14:58:05Zhttps://gitlab.isc.org/isc-projects/stork/-/issues/1323Attach more labels to the Prometheus samples2024-03-19T14:58:05ZSlawek FigielAttach more labels to the Prometheus samplesCurrently, if you haven't the subnet_cmds hook, the metrics are labeled with the subnet ID, and if you have the subnet_cmds hook, the metrics are labeled with the subnet name prefix if provided, otherwise with the subnet ID.
Our custome...Currently, if you haven't the subnet_cmds hook, the metrics are labeled with the subnet ID, and if you have the subnet_cmds hook, the metrics are labeled with the subnet name prefix if provided, otherwise with the subnet ID.
Our customer needs samples labeled by subnet ID regardless of the subnet_cmds presence. It would also be helpful to attach the shared network name.
[SF#1762](https://isc.lightning.force.com/lightning/r/Case/500S6000006AQSSIA4/view)1.17https://gitlab.isc.org/isc-projects/stork/-/issues/1322Upgrade Grafana and its dashboards2024-03-05T15:02:12ZSlawek FigielUpgrade Grafana and its dashboardsYou cannot import the example Grafana dashboards to a modern Grafana instance.
![image](/uploads/a95f33a1aa876ae18d92057fd933fc5f/image.png)
The Stork demo uses the `8.3.7` Grafana version. The latest version is `10.3.3`.
We should up...You cannot import the example Grafana dashboards to a modern Grafana instance.
![image](/uploads/a95f33a1aa876ae18d92057fd933fc5f/image.png)
The Stork demo uses the `8.3.7` Grafana version. The latest version is `10.3.3`.
We should upgrade the Grafana (and maybe Prometheus) used in the demo and migrate the example dashboards to a modern format.1.16https://gitlab.isc.org/isc-projects/stork/-/issues/1153add pool statistics to prometheus2023-09-12T13:48:16ZRazvan Becheriuadd pool statistics to prometheusnew stats have been added in 2.4.0:
v4:
```
"subnet[1].pool[0].assigned-addresses": [
[
0,
"2023-06-13 20:42:46.836205"
]
],
"subnet[1...new stats have been added in 2.4.0:
v4:
```
"subnet[1].pool[0].assigned-addresses": [
[
0,
"2023-06-13 20:42:46.836205"
]
],
"subnet[1].pool[0].cumulative-assigned-addresses": [
[
0,
"2023-06-13 20:42:46.836137"
]
],
"subnet[1].pool[0].declined-addresses": [
[
0,
"2023-06-13 20:42:46.836213"
]
],
"subnet[1].pool[0].reclaimed-declined-addresses": [
[
0,
"2023-06-13 20:42:46.836225"
]
],
"subnet[1].pool[0].reclaimed-leases": [
[
0,
"2023-06-13 20:42:46.836236"
]
],
"subnet[1].pool[0].total-addresses": [
[
11010049,
"2023-06-13 20:42:46.836128"
]
],
```
v6:
```
"subnet[1].pd-pool[0].assigned-pds": [
[
0,
"2023-06-13 21:28:57.196785"
]
],
"subnet[1].pd-pool[0].cumulative-assigned-pds": [
[
0,
"2023-06-13 21:28:57.196744"
]
],
"subnet[1].pd-pool[0].reclaimed-leases": [
[
0,
"2023-06-13 21:28:57.196789"
]
],
"subnet[1].pd-pool[0].total-pds": [
[
256,
"2023-06-13 21:28:57.196741"
]
],
"subnet[1].pool[0].assigned-nas": [
[
0,
"2023-06-13 21:28:57.196773"
]
],
"subnet[1].pool[0].cumulative-assigned-nas": [
[
0,
"2023-06-13 21:28:57.196739"
]
],
"subnet[1].pool[0].declined-addresses": [
[
0,
"2023-06-13 21:28:57.196775"
]
],
"subnet[1].pool[0].reclaimed-declined-addresses": [
[
0,
"2023-06-13 21:28:57.196779"
]
],
"subnet[1].pool[0].reclaimed-leases": [
[
0,
"2023-06-13 21:28:57.196783"
]
],
"subnet[1].pool[0].total-nas": [
[
281474976710656,
"2023-06-13 21:28:57.196736"
]
],
```
```backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/921Grafana DHCPv6 dashboard has some DHCPv4 data2022-12-13T14:52:52ZSlawek FigielGrafana DHCPv6 dashboard has some DHCPv4 dataThe issue was reported during 1.8.0 sanity checks by @slawek. [Source](https://gitlab.isc.org/isc-projects/stork/-/issues/910#note_335065)
The IPv4 data are visible on the "Stork Kea DHCPv6" Grafana dashboard.
![image](https://gitlab.i...The issue was reported during 1.8.0 sanity checks by @slawek. [Source](https://gitlab.isc.org/isc-projects/stork/-/issues/910#note_335065)
The IPv4 data are visible on the "Stork Kea DHCPv6" Grafana dashboard.
![image](https://gitlab.isc.org/isc-projects/stork/uploads/f9035edd5bfbdc980947cf97c7f89f93/image.png)backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/866Grafana Prometheus Dashboards need some datasource updates2022-12-07T10:21:55ZJens-Petter SalvesenGrafana Prometheus Dashboards need some datasource updatesThe datasource property is missing from some of the panels in the Grafana dashboards. Also, the dashboard id of Stork Kea DHCPv4 and Stork Kea DHCPv6 is shared, which makes importing them into grafana a little unsettling for a beginner.
...The datasource property is missing from some of the panels in the Grafana dashboards. Also, the dashboard id of Stork Kea DHCPv4 and Stork Kea DHCPv6 is shared, which makes importing them into grafana a little unsettling for a beginner.
Willing to make a quick fork.backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/774Missing Grafana links for IPv6 on dashboard2022-10-25T11:38:33ZSlawek FigielMissing Grafana links for IPv6 on dashboard![image](https://gitlab.isc.org/isc-projects/stork/uploads/3413238389d924d5b085501c8f0fefb2/image.png)
DHCPv6 subnets have no Grafana-link buttons on the dashboard.![image](https://gitlab.isc.org/isc-projects/stork/uploads/3413238389d924d5b085501c8f0fefb2/image.png)
DHCPv6 subnets have no Grafana-link buttons on the dashboard.backloghttps://gitlab.isc.org/isc-projects/stork/-/issues/341Self-documenting stats (--list-stats switch for agent)2021-06-01T08:44:42ZTomek MrugalskiSelf-documenting stats (--list-stats switch for agent)@matthijs and @tomek discussed the need to have a good statistics list for BIND 9. One way to achieve that would be to implement a `--list-stats` kind of command line switch. It would export the list of currently supported stats by the a...@matthijs and @tomek discussed the need to have a good statistics list for BIND 9. One way to achieve that would be to implement a `--list-stats` kind of command line switch. It would export the list of currently supported stats by the agent, along with some reasonably easy to understand, non-cryptic, non-overly abbreviated description.
For bonus points, that list could be in a format that could be integreated into Stork ARM.
This would address a real issue many BIND 9 users are having: BIND 9 has lots of stats, but nobody really knows what they mean. We won't solve the problem instantly. Incremental steps are the way to go.
We want to have something similar for Kea. However, Kea stats are well documented, so there is less pressing need for this (which also makes the issue easier to solve for Kea, by employing well proven copy-paste programming techniques) ;)backlog