Apivom Ping — operations dashboards for the Apivom platform
Ping is the operations dashboards layer behind the Apivom products. It shows operators the metrics Otto collects, with dashboards provisioned as code and sign-in through Key. Ping is included with the products and is not sold separately.
Infrastructure layerMetrics are easier to act on when you can see them
Ping turns the numbers Otto collects into dashboards for the people who run the platform, starting with object storage.
Dashboards over Otto’s metrics
Ping reads the metrics Otto collects and draws them as dashboards, so operators look at charts instead of raw numbers.
Provisioned as code
Dashboards are defined as files and provisioned automatically, so they are part of the platform configuration instead of something drawn by hand.
A dashboard for object storage
Today Ping ships one provisioned dashboard, for Apivom Blob object storage, kept in the Apivom folder.
Single sign-in through Key
Operators sign in through Key. Key roles are mapped to Ping roles: admin, editor and viewer.
Built for operators
Ping is an internal tool for the people who run the Apivom platform. It has no customer-facing dashboards, and no product depends on it.
Alongside Otto and Odin
Otto collects metrics and sends alerts, Odin tracks errors and traces, and Ping is where operators look at the numbers over time.
How Apivom operates the products with Ping
You do not set Ping up on its own. Apivom operators use it to look at how the platform behaves. Today that means one provisioned dashboard, for object storage, fed by the metrics Otto collects from Blob.
- Blob storage dashboard. A provisioned dashboard for Apivom Blob object storage, in the Apivom folder.
- Numbers from Otto. Ping does not collect anything itself. Its data source is Otto, which collects metrics from Blob like the other services.
- Nothing for customers to configure. Ping is used by Apivom operators only. No product depends on it to work.
Sign-in and roles through Key
Operators do not keep a separate Ping account. They sign in through Key, and the roles they hold in Key decide what they can do in Ping.
- Single sign-in. Ping opens through Key, like the other Apivom tools.
- Admin, editor, viewer. Client roles in Key are mapped to the three Ping roles.
- Checked sign-in flow. Sign-in uses PKCE, refresh tokens and ID-token validation.
Frequently asked questions
What is Apivom Ping?
Ping is operations dashboards for the Apivom platform. It draws the metrics that Otto collects as dashboards, which are provisioned as code. Apivom operators open it through single sign-in with Key.
Is Ping sold separately?
No. Ping is an infrastructure layer that is included with the Apivom products. You do not buy or set it up on its own. If you want to know how Apivom operates the platform behind the products, talk to us.
Which dashboards exist today?
One provisioned dashboard is active today: Apivom Blob object storage, kept in the Apivom folder and fed by the metrics Otto collects from Blob.
Where does Ping get its data?
From Otto. Otto collects the metrics from the hosts and services, and Ping reads them as its data source. Ping does not collect metrics of its own.
Who can sign in to Ping?
Apivom operators, through Key. Roles held in Key are mapped to admin, editor and viewer in Ping. Customer-facing dashboards are not part of what Ping offers today.
How does Ping relate to Apivom Otto and Apivom Odin?
Otto collects the metrics and sends alerts by email. Ping is the dashboard layer that shows those metrics. Odin tracks errors and traces. Ping does not send alerts of its own.
See the platform the way its operators do
Ping comes with the Apivom products. Talk to us about how Apivom keeps an eye on the platform your work runs on.