Skip to main content
Glama
Zabbix MCP Server

Zabbix MCP Server

apmlog_get

Read-only

Retrieves OpenTelemetry APM log records from Zabbix by required time range, then filters by trace ID, span ID, severity, or resource, scope, and log attributes for targeted troubleshooting.

Instructions

Retrieve OpenTelemetry (OTel) APM log records (Zabbix 8.0+): logs with severity_text, severity_number, body, service_name, and the trace / span they were produced in. time_from and time_till are required. Filter by traceids, spanids, trace flags (with_flags_on / with_flags_off, sum of flag values), severity_numbers (0 to 24, through extra_params) or resource / scope / log attribute conditions. Page with limit and offset. For a user who is not Super admin the result is limited to the data whose resource attributes match an APM filter of one of the user's groups (usergroup 'apm_filters').

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of records to return.
filterNoReturn only results whose properties exactly match the given values (a single value or a list of values per key). Example: {"status": 0} or {"status": [0, 1]}. Keys: body, event_name, log_attributes, resource_attributes, resource_schema_url, scope_attributes, scope_name, scope_schema_url, scope_version, service_name, severity_number, severity_text, spanid, timestamp, trace_flags, traceid. Text properties cannot be filtered; use 'search' for them.
offsetNoNumber of records to skip before returning the result (paging).
outputNoProperties of the apmlog object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: timestamp, traceid, spanid, service_name, severity_text, body. Properties: body, event_name, log_attributes, resource_attributes, resource_schema_url, scope_attributes, scope_name, scope_schema_url, scope_version, service_name, severity_number, severity_text, spanid, timestamp, trace_flags, traceid.
searchNoReturn results whose string properties contain the given pattern (case-insensitive; '*' is a wildcard when searchWildcardsEnabled is true). Example: {"name": "web"}. Keys: body, event_name, resource_schema_url, scope_name, scope_schema_url, scope_version, service_name, severity_text, spanid, traceid.
serverNoTarget Zabbix server. Available: default. Defaults to 'default' if omitted.
spanidsNoReturn only log records produced during the given spans.
raw_jsonNoStrips the security disclaimer preamble from the response so it is pure JSON. Default: false. Requires the bearer token to have 'allow_raw_json' explicitly enabled by an operator in the admin portal - tokens without that policy receive a PolicyError instead. WARNING: setting true bypasses the prompt-injection mitigation marker that wraps untrusted Zabbix data (host names, item descriptions, problem text). LLM clients (Claude, GPT, Cursor, ...) should leave this false; only programmatic non-LLM consumers (Python scripts, n8n workflows that json.loads the result) should set true.
traceidsNoReturn only log records produced during the given traces.
sortfieldNoSort by one or more of: timestamp, traceid, spanid, trace_flags, severity_text, severity_number, service_name, resource_schema_url, scope_schema_url, scope_name, scope_version, event_name (a list for several; pair with 'sortorder'). No other property is sortable.
sortorderNoSort order: 'ASC' or 'DESC'.
time_fromYesReturn only log records of events that occurred at or after this time (required). Unix timestamp, ISO 8601 date-time or a relative time such as now-1h or now-1d/d.
time_tillYesReturn only log records of events that occurred before this time (required). Unix timestamp, ISO 8601 date-time or a relative time such as now or now/d.
extra_paramsNoOther native apmlog.get parameters, merged into the request as-is. Parameters: severity_numbers. Any other key is refused here, because Zabbix would silently ignore it. For a parameter you are sure exists on your release but is not listed, use zabbix_raw_api_call.
with_flags_onNoReturn only records that have all of these trace flags set (sum of flag values).
log_attributesNoLog attributes: Attribute conditions as a list of {"key": ..., "value": ..., "operator": ...} objects; operators: 0 Contains, 1 Equals, 2 Not like, 3 Not equal, 4 Exists, 5 Does not exist. An empty list returns everything.
with_flags_offNoReturn only records that have none of these trace flags set (sum of flag values).
scope_attributesNoScope attributes: Attribute conditions as a list of {"key": ..., "value": ..., "operator": ...} objects; operators: 0 Contains, 1 Equals, 2 Not like, 3 Not equal, 4 Exists, 5 Does not exist. An empty list returns everything.
resource_attributesNoResource attributes: Attribute conditions as a list of {"key": ..., "value": ..., "operator": ...} objects; operators: 0 Contains, 1 Equals, 2 Not like, 3 Not equal, 4 Exists, 5 Does not exist. An empty list returns everything.
log_attributes_evaltypeNoHow the conditions in log_attributes combine: 0 = And/Or (default), 2 = Or.
scope_attributes_evaltypeNoHow the conditions in scope_attributes combine: 0 = And/Or (default), 2 = Or.
resource_attributes_evaltypeNoHow the conditions in resource_attributes combine: 0 = And/Or (default), 2 = Or.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv1.42.2
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / extra_params / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "countOutput",
      +        "excludeSearch",
      +        "searchByAny",
      +        "searchWildcardsEnabled",
      +        "startSearch",
      +        "severity_numbers"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / extra_params / description
      Previous value: -"Other native apmlog.get parameters, merged into the request as-is. apmlog.get has no parameters beyond the typed ones. Any other key is refused here, because Zabbix would silently ignore it. For a parameter you are sure exists on your release but is not listed, use zabbix_raw_api_call."New value: +"Other native apmlog.get parameters, merged into the request as-is. Parameters: severity_numbers. Any other key is refused here, because Zabbix would silently ignore it. For a parameter you are sure exists on your release but is not listed, use zabbix_raw_api_call."
    • changedInput schema / properties / filter / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "body",
      +        "event_name",
      +        "log_attributes",
      +        "resource_attributes",
      +        "resource_schema_url",
      +        "scope_attributes",
      +        "scope_name",
      +        "scope_schema_url",
      +        "scope_version",
      +        "service_name",
      +        "severity_number",
      +        "severity_text",
      +        "spanid",
      +        "timestamp",
      +        "trace_flags",
      +        "traceid"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "extend",
      +      "count"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "body",
      +        "event_name",
      +        "log_attributes",
      +        "resource_attributes",
      +        "resource_schema_url",
      +        "scope_attributes",
      +        "scope_name",
      +        "scope_schema_url",
      +        "scope_version",
      +        "service_name",
      +        "severity_number",
      +        "severity_text",
      +        "spanid",
      +        "timestamp",
      +        "trace_flags",
      +        "traceid"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / output / description
      Previous value: -"Properties of the apmlog object to return. Pass 'extend' for all, 'count' for the number of matches only, or a comma-separated list of property names. Default when omitted: timestamp, traceid, spanid, service_name, severity_text, body. Properties: body, event_name, log_attributes, resource_attributes, resource_schema_url, scope_attributes, scope_name, scope_schema_url, scope_version, service_name, severity_number, severity_text, spanid, timestamp, trace_flags, traceid."New value: +"Properties of the apmlog object to return. Pass 'extend' for all, 'count' for the number of matches only, or a list of property names. Default when omitted: timestamp, traceid, spanid, service_name, severity_text, body. Properties: body, event_name, log_attributes, resource_attributes, resource_schema_url, scope_attributes, scope_name, scope_schema_url, scope_version, service_name, severity_number, severity_text, spanid, timestamp, trace_flags, traceid."
    • changedInput schema / properties / search / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "propertyNames": {
      +      "enum": [
      +        "body",
      +        "event_name",
      +        "resource_schema_url",
      +        "scope_name",
      +        "scope_schema_url",
      +        "scope_version",
      +        "service_name",
      +        "severity_text",
      +        "spanid",
      +        "traceid"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "timestamp",
      +      "traceid",
      +      "spanid",
      +      "trace_flags",
      +      "severity_text",
      +      "severity_number",
      +      "service_name",
      +      "resource_schema_url",
      +      "scope_schema_url",
      +      "scope_name",
      +      "scope_version",
      +      "event_name"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "timestamp",
      +        "traceid",
      +        "spanid",
      +        "trace_flags",
      +        "severity_text",
      +        "severity_number",
      +        "service_name",
      +        "resource_schema_url",
      +        "scope_schema_url",
      +        "scope_name",
      +        "scope_version",
      +        "event_name"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / sortfield / description
      Previous value: -"Sort by one or more of: timestamp, traceid, spanid, trace_flags, severity_text, severity_number, service_name, resource_schema_url, scope_schema_url, scope_name, scope_version, event_name (comma-separated for several; pair with 'sortorder'). No other property is sortable."New value: +"Sort by one or more of: timestamp, traceid, spanid, trace_flags, severity_text, severity_number, service_name, resource_schema_url, scope_schema_url, scope_name, scope_version, event_name (a list for several; pair with 'sortorder'). No other property is sortable."
    • changedInput schema / properties / sortorder / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "ASC",
      +      "DESC"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "enum": [
      +        "ASC",
      +        "DESC"
      +      ],
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "result": {
      -      "title": "Result",
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "result"
      -  ],
      -  "title": "apmlog_getOutput",
      -  "type": "object"
      -}New value: +null
  2. First observedv1.41.0

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds meaningful behavioral context beyond that: Zabbix 8.0+ requirement, required time bounds, severity range 0-24 via extra_params, trace-flag semantics, and the usergroup 'apm_filters' restriction for non-Super-admin users. It does not cover rate limits or response/error behavior, but it adds substantive operational detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded, organized, and free of filler, with the resource and required constraints stated early. It is appropriately sized for a 22-parameter tool, though it repeats some details already present in the schema and the filter list makes it dense.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex read-only APM log query with no output schema, the description covers the resource, required time bounds, filtering, paging, access limitations, and version applicability. It does not fully describe the response envelope or count-mode behavior, but output selection is documented in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema already documents nearly all parameter meaning. The description reinforces required time parameters and filter classes and adds the 0-24 severity_numbers range, but most parameter semantics are already carried by the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Retrieve OpenTelemetry (OTel) APM log records', naming the key fields and trace/span relationship. The purpose is clear, but it does not explicitly contrast with siblings such as apmtrace_get or apmspan_get, so sibling differentiation is implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives useful usage constraints: time_from and time_till are required, filtering options are listed, paging is explained, and non-Super-admin access is limited by APM filters. However, it never explicitly says when to use this tool instead of apmtrace_get, apmspan_get, or other log/history retrieval tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.