Open sebastianw opened 3 years ago
:+1:
In addition the http endpoint could serve the json. Alternatively someone could build an orchestrator that creates metrics from logs (white-box approach) like I did with https://github.com/ties/rpki-client-web but a first party solution would be a lot better imo.
I understand this is important, but I'm not going to be able to squeeze it in my schedule in the near future.
Will report again in one month or earlier.
Closest effort is a fork that I've done a months ago, precisely using a customized C library based on that offered by DigitalOcean. Due to l a lack of time, I still can't finish it, but any help is really appreciated :)
The fork is at https://github.com/pcarana/FORT-validator, still needs some checks and also to define what data will be reported.
@pcarana Ok, thank you.
This is still far from feasible. Will report again in September or earlier.
I too would greatly appreciate this feature, it's currently holding us back from retiring octorpki in favor of fort.
Me too! :-)
Question: Why do you need this?
I have a prototype, but it only tracks a small amount of statistics. I'm going to have to release 1.5.2 soon, so I'm debating whether I should include the prototype or not.
Hello,
currently there is no way to get validation statistics out of FORT. It would be nice if you could provide a prometheus HTTP endpoint for it.
The format is described here:
https://prometheus.io/docs/instrumenting/exposition_formats/
Also there seems to be a C library for it:
https://github.com/digitalocean/prometheus-client-c
Maybe you could also take a look a the metrics that Routinator exports so that there is similarity between the endpoints:
https://routinator.docs.nlnetlabs.nl/en/stable/monitoring.html