Query server for exposed Prometheus metrics in 1Password Connect
A documented 1Password Connect operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Query server for exposed Prometheus metrics
- GETReads data · Metrics
1password.local/metrics
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which 1Password Connect operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other 1Password Connect operations
- Create a new ItemPOST · changes data
- Delete an ItemDELETE · changes data
- Update a subset of Item attributesPATCH · changes data
- Update an ItemPUT · changes data
- Retrieve a list of API Requests that have been madeGET · reads data
- Get all the files inside an ItemGET · reads data
- Get the details of an ItemGET · reads data
- Get state of the server and its dependenciesGET · reads data
Questions
- Can HumDay query server for exposed prometheus metrics in 1Password Connect?
- Yes. This operation is published in 1Password Connect's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my 1Password Connect account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in 1Password Connect.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your 1Password Connect account.
Where this came from
Read from a published API description for 1Password Connect at i.1password.com/media/1password-connect/1password-connect-api.yaml. The description above is the provider’s own wording, not ours. Last published 2023-02-27.