Agenetix

Manage & Operate

Operate & monitor

Logs, catalog status, analytics, and operational workflows for running Agenetix in production.

5 sections

This guide covers the day-to-day workflows for keeping your MCP servers and agents healthy.

Catalog status#

Every MCP server shows a catalog status that tracks whether the live runtime matches your stored tool catalog:

StatusMeaningWhat to do
In syncLive server matches your catalogNothing needed
Out of syncDifferences detectedRedeploy (generated) or rediscover (connected)
Needs redeployTool rules changed since last publishClick Publish to apply changes
UnreachableAgenetix could not reach the serverCheck that your server is running and the URL is correct

Request logs#

Every tool call routed through Agenetix is logged with:

  • Tool name
  • Duration in milliseconds
  • Success or failure status
  • Error message (if any)
  • Who triggered the call
  • Timestamp

View logs on the server detail page under the Logs tab.

Analytics#

The analytics dashboard gives you a high-level view of your server's usage:

  • Daily invocation counts (success vs failure)
  • Average latency trends
  • Top tools by usage volume
  • Error rate over time

Access analytics from the server detail page under the Analytics tab, or select a time range (7, 14, or 30 days).

Configuration updates#

Agenetix separates server configuration into distinct areas so changes in one area cannot accidentally affect another:

MERMAID
flowchart TD
    Identity["Server identity\nname, description"] --> Server["MCP Server"]
    Source["API source\nOpenAPI spec URL"] --> Server
    ToolCat["Tool rules\nper-tool settings"] --> Server
    Runtime["Runtime config\nauth, hosting, Gateway"] --> Server

Each area has its own save action. For example, editing a tool's description does not affect the server's hosting configuration, and refreshing the OpenAPI spec does not overwrite your tool rules.

Redeploy checklist#

When the catalog status shows Needs redeploy:

  1. Review what changed in the Tools tab
  2. If using hosted Gateway mode, click Publish to redeploy
  3. If self-hosting, download the updated server ZIP and redeploy
  4. Verify the catalog status returns to In sync