Infrastructure Observability post installation
After completing the Infrastructure Observability (IO) installation, the following optional configurations can be performed to extend functionality. These steps are not required for basic operation but are recommended for enabling AI-powered interactions and ensuring accurate topology visualization.
Configure the MCP server in IO (optional)
The Model Context Protocol (MCP) Server allows AI agents to connect to your Virtana IO data using natural-language prompts. By configuring the MCP extension, you enable secure communication between an AI client (such as Goose) and your IO Server's underlying APIs via a Streamable HTTP endpoint. You need your IO server URL and an API token. The setup involves adding a custom extension in your MCP client with the IO endpoint and an authorization header. See Configure MCP Server in IO for details.
IO Topology enable (optional)
IO entity topology defines how entities (such as hosts, VMs, and connected infrastructure) are visualized with their parent, host, and related entities in the inventory. In some cases, topology may not form correctly because the collectRelationship parameter is not enabled by default in collection policies. This section provides scripts to fix topology issues and enable custom property synchronization with Global View. See IO custom scripts for details.