Discover new interfaces
Build an inventory of REST endpoints, MCP tools and A2A metadata seen in connected telemetry. Review new interfaces and changes against your declared baseline.
Turn connected API and MCP traffic into an inventory you can explore, activity you can investigate, and access decisions you can manage. Built around the gateways you already use.
research-agent→tools/call→internal-search
agent call→tool response→related finding
gateway identity→local Policy→allow / deny
Connect to the gateway
you already run.
Understand what is connected, what changed, and which activity needs a closer look.
Build an inventory of REST endpoints, MCP tools and A2A metadata seen in connected telemetry. Review new interfaces and changes against your declared baseline.
Follow captured calls and responses. Bring related gateway, Falco and Suricata events together to understand the evidence behind a finding.
Bind a subject to its authenticated gateway identity. Manage agent and endpoint access in Alertflex, with recorded decisions and enforcement through configured gateway routes.
ACTUAL OPENSEARCH DASHBOARDS · LAB DATA
Start with telemetry and OpenSearch. Add the Alertflex console when your team needs shared inventory, traces and access management.
Gateway logs and supported connectors bring HTTP activity into Altprobe. Add Falco or Suricata events where you need host and network context.
Altprobe normalizes supported events into OCSF for OpenSearch and supplies observed inventory and matched traces to Alertflex.
Import CycloneDX reports from configured Trivy scans of projects or container images. Explore component inventory in Alertflex and vulnerability findings in OpenSearch.
Use the console to inspect evidence and set access decisions. A local Policy listener supplies decisions to protected gateway routes.
Telemetry analysis is asynchronous. Policy authorization is a separate, synchronous path on configured routes; console changes take effect after inventory polling.
Six gateway labs and reusable connectors. Choose a familiar entry point and build from there.
Evaluate with local, synthetic traffic before connecting your own environment.
A ready-to-run Linux collector, reusable integrations and OpenSearch dashboards. Get a working lab without an Alertflex account.
git clone https://github.com/olegzhr/altprobe.git
Use Alertflex to organize observed assets, examine traces and incidents, and manage configured access decisions from one console.
No one-size-fits-all promise. We scope a deployment around your sources, topology and operating requirements.
A clear scope makes a better evaluation. Here is how the pieces fit together.
Have a different question?Altprobe collector binaries, connectors and labs are available under Apache-2.0. You can evaluate collection, OCSF output and dashboards locally. Contact us to discuss Alertflex deployment and support.
Visibility depends on the sources you connect and the fields they capture. Supported gateway integrations expose network-based API and MCP interactions.
No. Telemetry analysis runs after capture. When you enable Policy for protected routes, the gateway makes a separate synchronous authorization call. A finding raised later cannot undo an already completed request. Inventory polling also means a console change is not applied instantly.
Altprobe can run in your environment and send supported events to your OpenSearch deployment. Alertflex receives the inventory, traces and incident data enabled in your configuration.
Start with one of the six gateway labs and its shared tests. Then run a scoped pilot on representative traffic.
Tell us about your gateways, agents and deployment needs. We will help define a focused first step.