This commit finalizes the documentation improvement plan by: - Centralizing reference material in README.md. - Creating a dedicated Technical Maintenance guide (docs/howtos/maintenance.md). - Creating a categorized Sample Queries & Mutations overview (docs/queries/README.md). - Eliminating redundant information across the doc set (DRY principle). - Optimizing cross-references between reference documentation and the Cookbook. - Updating the improvement plan to reflect all tasks as completed.
3.8 KiB
Zabbix GraphQL API Cookbook
This cookbook provides step-by-step "recipes" for common tasks. These instructions are designed to be easy for humans to follow and structured enough for AI agents (using the MCP server) to generate test cases.
🤖 AI-Based Test Generation
To generate a test case from a recipe:
- Start the
zabbix-graphqlMCP server. - Provide the recipe to your AI agent.
- Ask the agent to "Implement a test case for this recipe using the Zabbix GraphQL API".
- The agent will use the MCP server to explore the schema and generate appropriate GraphQL operations.
🍳 Recipe: Extending Schema with a New Device Type
This recipe shows how to add support for a new specialized device type without modifying the core API code.
Prerequisites
- Zabbix Template Group
Templates/Roadwork/Devicesexists. - Zabbix GraphQL API is running.
Step 1: Define the Schema Extension
Create a new .graphql file in schema/extensions/ (e.g. distance_tracker.graphql):
type DistanceTrackerDevice {
id: String
name: String
location: Location
distance: Float
batteryLevel: Float
lastSeen: DateTime
}
Step 2: Configure Environment Variables
Add the new schema and resolver to your .env file:
ADDITIONAL_SCHEMAS=./schema/extensions/distance_tracker.graphql
ADDITIONAL_RESOLVERS=DistanceTrackerDevice
Restart the API server.
Step 3: Import the Template
Execute the importTemplates mutation to create the template in Zabbix. Use Zabbix item keys that match your GraphQL fields (e.g. distance.current for distance).
Reference: See how items map to fields in the Zabbix to GraphQL Mapping.
🍳 Recipe: Provisioning a New Host
Prerequisites
- A target Host Group exists in Zabbix.
- At least one Template exists in Zabbix.
Step 1: Prepare the Host Object
Define the host name, groups, and templates to link.
Step 2: Execute createHost Mutation
For more details on the input fields, see the Reference: createHost.
mutation CreateNewHost($host: String!, $groups: [Int!]!, $templates: [Int!]!) {
createHost(host: $host, hostgroupids: $groups, templateids: $templates) {
hostids
error {
message
}
}
}
🍳 Recipe: Managing User Permissions
Step 1: Create Permission Template Group
Create a template group with the prefix Permissions/ in Zabbix (e.g. Permissions/Read-Only-Access).
Step 2: Assign to User Group
In Zabbix, give a User Group Read access to this template group.
Step 3: Verify via API
query CheckMyPermissions {
hasPermissions(permissions: [
{ objectName: "Read-Only-Access", permission: READ }
])
}
🍳 Recipe: Bulk Import of Templates and Hosts
This recipe guides you through performing a mass import of multiple templates and hosts in a single operation.
Step 1: Prepare Template Import
Use the importTemplates mutation. You can provide multiple template definitions in the templates array.
Step 2: Prepare Host Import
Use the importHosts mutation. Link them to the newly imported templates using their names or IDs.
Step 3: Combined Operation (Optional)
You can execute both mutations in a single GraphQL request to ensure atomic-like provisioning of your infrastructure.
mutation BulkProvisioning($templates: [CreateTemplate!]!, $hosts: [CreateHost!]!) {
importTemplates(templates: $templates) {
templateid
host
message
}
importHosts(hosts: $hosts) {
hostid
deviceKey
message
}
}
For detailed examples of the input structures, refer to Sample Import Templates and Sample Import Hosts.