tracker.org
This commit is contained in:
parent
c80a5bbcd0
commit
cb8a685d65
1 changed files with 32 additions and 1 deletions
33
tracker.org
33
tracker.org
|
@ -1330,7 +1330,7 @@ CLOCK: [2021-11-03 Wed 08:28]--[2021-11-03 Wed 09:59] => 1:31
|
|||
*** 2021-11-04 Thursday
|
||||
**** MEETING Weekly meeting :work:meeting:
|
||||
:LOGBOOK:
|
||||
CLOCK: [2021-11-04 Thu 17:00]
|
||||
CLOCK: [2021-11-04 Thu 17:00]--[2021-11-05 Fri 09:09] => 16:09
|
||||
:END:
|
||||
[2021-11-04 Thu 17:00]
|
||||
- ref ::
|
||||
|
@ -1393,3 +1393,34 @@ CLOCK: [2021-11-04 Thu 09:51]--[2021-11-04 Thu 12:07] => 2:16
|
|||
CLOCK: [2021-11-04 Thu 09:20]--[2021-11-04 Thu 09:51] => 0:31
|
||||
:END:
|
||||
[2021-11-04 Thu 09:50]
|
||||
|
||||
*** 2021-11-05 Friday
|
||||
**** EMAIL Help John doing a cron :work:email:
|
||||
:LOGBOOK:
|
||||
CLOCK: [2021-11-05 Fri 09:09]
|
||||
:END:
|
||||
[2021-11-05 Fri 09:09]
|
||||
- ref :: mail: How can I query an IROH endpoint programatically?
|
||||
|
||||
#+begin_quote
|
||||
On 4 Nov 2021, at 22:23, John Jardine (johjardi) <johjardi@cisco.com> wrote:
|
||||
|
||||
Hi,
|
||||
|
||||
To support iroh-incident scaling based on a queue-depth metric ( Tenzin Issue 1553 ) I am thinking about creating a task that will be run every N minutes to query the endpoint. To do this the task would have to authenticate and I don’t know how to do that for an automated tool. Not sure if the route makes a difference, the metrics are available here: /iroh/admin/queue/status-report/incidents
|
||||
|
||||
Can you give me any guidance or point me to any docs on how to do this?
|
||||
|
||||
Thanks,
|
||||
John J.
|
||||
#+end_quote
|
||||
|
||||
|
||||
|
||||
Hi John,
|
||||
|
||||
The endpoint will not be `/iroh/admin/…` but `/admin/…` which mean it is only reachable via the VPN, but I guess you will make the request from the internal network. So you should be able to reach https://iroh-adm.int.iroh.site/admin/ directly.
|
||||
|
||||
In order to make a call you need an OAuth2 client with the following scope:
|
||||
|
||||
iroh-master/queue/incidents:read
|
||||
|
|
Loading…
Reference in a new issue