Ispi Admin - Client

For day-to-day operations, this view allows you to:

Ask a veteran admin about the ISPI Admin Client, and they won't praise it. They'll tell you a war story.

"Remember the 'Black Friday Incident'? The web dashboard showed everything green. But the ISPI client? Node 04 had a red 'D' next to its queue depth. One double-click later, we saw the deadlock. Fixed it by terminating a single stalled worker. Total downtime: 11 seconds."

That’s the relationship. It’s not love. It’s respect. The client doesn’t hold your hand. It doesn't generate fancy PDF reports. It gives you the raw, unfiltered state of your processing universe and gets out of your way. ispi admin client

Unauthorized access to the ISPI Admin Client can lead to catastrophic billing errors. The client supports integration with LDAP (Active Directory) and SAML 2.0.

| Role | Permissions | | :--- | :--- | | ispi-monitor | Read-only: View topology and logs. | | ispi-operator | Start/stop nodes, view subscribers. | | ispi-config | Modify pipelines, price plans, and event maps. | | ispi-admin | Full control: Add/remove nodes, manage security, deploy applications. |

Upon launch, the client will populate its local cache. This can take 2–5 minutes depending on the size of your topology. You will see a dashboard featuring: For day-to-day operations, this view allows you to:

Pro Tip: For headless Linux servers, use the wsadmin.sh script located in the bin/ directory to run administrative commands without launching the GUI.

The iSPI Admin Client is a specialized user interface or dashboard used to manage iSPI components. Unlike the main network map, which shows device status, the Admin Client focuses on the backend logic. It enables administrators to handle the "intelligence" of the monitoring system—specifically how different services, protocols, and data feeds are integrated.

Unlike modern "admin panels" that hide destructive buttons behind three confirmation dialogs, the ISPI Admin Client assumes you know what you’re doing. That’s dangerous. And that’s the point. Pro Tip: For headless Linux servers, use the wsadmin

With a few clicks, you can:

The most interesting feature? The Session Spelunker. It lets you rewind any failed process, step through its logic backwards, and see exactly which data element turned bad. Not a stack trace—a full forensic replay.