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/998Not working Grafana dashboard2023-03-03T10:37:41ZVojtech DusatkoNot working Grafana dashboard---
name: Bug report
about: Create a report to help us improve
---
**Describe the bug**
I tried to use grafana kea-dhcp4 dashboard but without success. There were no option to select prometheus datasource and nothing were displayed, ju...---
name: Bug report
about: Create a report to help us improve
---
**Describe the bug**
I tried to use grafana kea-dhcp4 dashboard but without success. There were no option to select prometheus datasource and nothing were displayed, just an error.
**To Reproduce**
Steps to reproduce the behavior:
1. Install Grafana v9.3.1
2. Include prometheus datasource with kea data scraped via stork agent
3. Import dashboard from master branch ... https://gitlab.isc.org/isc-projects/stork/-/blob/master/grafana/kea-dhcp4.json
**Expected behavior**
Dashboard with data which asks to datasource while importing it, not broken dashboard
**Environment:**
Described above (grafana v9.3.1)
**Additional Information**
![2023-02-26_17-17-25](/uploads/a6bd32e716a0e7699d278a64397d886b/2023-02-26_17-17-25.png)
**Some initial questions**
- Are you sure your feature is not already implemented in the latest Kea version? Yup
- Are you sure what you would like to do is not possible using some other mechanisms? Yup
- Have you discussed your idea on kea-users or kea-dev mailing lists? Nope
**Is your feature request related to a problem? Please describe.**
Nope, it's just a buggy dashboard JSON
**Describe the solution you'd like**
Improved dashboard which will display data
**Describe alternatives you've considered**
N/A
**Additional context**
N/A
**Funding its development**
Not yet, maybe fix the issue by myself.
**Participating in development**
**Contacting you**
vojtech@dusatko.org or just reply herehttps://gitlab.isc.org/isc-projects/stork/-/issues/980Stork Grafana Links do not honor path from Grafana URL setting2023-03-28T11:58:01ZCarsten StrotmannStork Grafana Links do not honor path from Grafana URL settingStork 1.9.0 from ISC packages
I have Grafana running on the same machine as Stork. Both are behind a NGINX reverse proxy. Stork is available on the root of the webserver:
http://machine.tld/
Grafana is available in a sub/path
http://...Stork 1.9.0 from ISC packages
I have Grafana running on the same machine as Stork. Both are behind a NGINX reverse proxy. Stork is available on the root of the webserver:
http://machine.tld/
Grafana is available in a sub/path
http://machine.tld/grafana/
I have configured the Grafana path in the Stork settings, but Stork generates links that do not point to the Grafana Path:
http://machine.tld/d/hRf18FvWz/?var-subnet=1000&var-instance=stork-demo%3A9547
Result is an empty page from Stork when using such link.1.10Slawek FigielSlawek Figielhttps://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/470Tooltips for Grafana links2021-03-02T07:56:31ZTomek MrugalskiTooltips for Grafana linksA customer reported that the Grafana links in Stork dashboard. It was confusing what it is about. He suggested to have a tooltip that explains what the icon/link does.A customer reported that the Grafana links in Stork dashboard. It was confusing what it is about. He suggested to have a tooltip that explains what the icon/link does.0.15Tomek MrugalskiTomek Mrugalskihttps://gitlab.isc.org/isc-projects/stork/-/issues/469DHCPv6 dashboard for Grafana2021-03-12T18:08:46ZTomek MrugalskiDHCPv6 dashboard for GrafanaA customer is interested in DHCPv6 dashboard. He came up with one on his own.A customer is interested in DHCPv6 dashboard. He came up with one on his own.0.16Michal NowikowskiMichal Nowikowskihttps://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) ;)backloghttps://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/176prepare DHCPv6 dashboard for Grafana2021-03-24T10:43:24ZMichal Nowikowskiprepare DHCPv6 dashboard for GrafanaA dashboard template should be prepared for Grafana.A dashboard template should be prepared for Grafana.0.16Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/stork/-/issues/167integrate stork with prometheus2020-03-02T13:46:24ZMichal Nowikowskiintegrate stork with prometheus0.5Michal NowikowskiMichal Nowikowskihttps://gitlab.isc.org/isc-projects/stork/-/issues/92Req 4.1 - DORA graph per server2021-03-05T18:26:37ZVicky Riskvicky@isc.orgReq 4.1 - DORA graph per serverI would like to see a time series line graph displaying the # of each type of dhcp request (depending on whether v4 or v6) on a per-server basis. This will help me quickly identify when there is an anomaly, such as a client or class of ...I would like to see a time series line graph displaying the # of each type of dhcp request (depending on whether v4 or v6) on a per-server basis. This will help me quickly identify when there is an anomaly, such as a client or class of clients that is sending many repeated requests, or a connectivity problem, causing a server to stop receiving discovers, for example.1.0-backlogVicky Riskvicky@isc.orgVicky Riskvicky@isc.orghttps://gitlab.isc.org/isc-projects/stork/-/issues/78Req 10.1.5 - Modify Grafana2020-04-01T10:27:16ZVicky Riskvicky@isc.orgReq 10.1.5 - Modify GrafanaUser may wish to rearrange data in the Grafana interface in order to investigate possible relationship between different metrics, perhaps to troubleshoot performance anomalies. If Stork somehow disables my ability to create new queries a...User may wish to rearrange data in the Grafana interface in order to investigate possible relationship between different metrics, perhaps to troubleshoot performance anomalies. If Stork somehow disables my ability to create new queries and dashboards in Grafana, that would be super-annoying.0.6https://gitlab.isc.org/isc-projects/stork/-/issues/76Req 10.1.3 - Standalone use of Prometheus and Grafana2020-06-18T16:21:50ZVicky Riskvicky@isc.orgReq 10.1.3 - Standalone use of Prometheus and GrafanaThe user is already using Prometheus and Grafana with other network elements and does not wish to add a new GUI (Stork). Some users will want to use the Prometheus exporter and Grafana template without Stork. If this project can deliver ...The user is already using Prometheus and Grafana with other network elements and does not wish to add a new GUI (Stork). Some users will want to use the Prometheus exporter and Grafana template without Stork. If this project can deliver supported modules for these two popular open source projects, that would be valuable.0.9Vicky Riskvicky@isc.orgVicky Riskvicky@isc.orghttps://gitlab.isc.org/isc-projects/stork/-/issues/14Come up with initial Stork dashboard2019-11-16T10:10:17ZTomek MrugalskiCome up with initial Stork dashboardThe goal of this issue is to come up with an initial Stork dashboard. It doesn't have to be perfect, the idea is to have something there and then evolve it over time.The goal of this issue is to come up with an initial Stork dashboard. It doesn't have to be perfect, the idea is to have something there and then evolve it over time.Stork-0.2