imbi-plugin-logzio
Logz.io provider for the Imbi project logs tab, surfacing relevant logs without requiring search knowledge.
Installation
pip install imbi-plugin-logzio
Configuration
Create a Logz.io Integration in Imbi and enable its Logs capability. Connection settings and the API token live on the Integration; the query-shaping settings are scoped to the Logs capability.
Integration Options
| Name | Label | Default | Description |
|---|---|---|---|
region |
Region | us |
Logz.io account region. One of us, eu, uk, au, ca. |
timeout_seconds |
Request Timeout | 15 |
Per-request timeout in seconds. |
Logs Capability Options
| Name | Label | Default | Description |
|---|---|---|---|
base_query |
Base Query Template | — | Elasticsearch query_string applied as a must clause. Supports ${project_slug}, ${org_slug}, ${team_slug}, ${environment}, ${project_id}, ${project_type_slug}. |
timestamp_field |
Timestamp Field | @timestamp |
Source field containing the log timestamp. |
message_field |
Message Field | message |
Source field containing the log message. |
level_field |
Level Field | level |
Source field containing the log severity level. |
environment_field |
Environment Field | — | Log field used to filter by environment. Leave blank to disable automatic environment filtering. |
default_environments |
Default Environments | — | Comma-separated environments pre-selected in the UI. |
Region → Hostname
| Region | API Host |
|---|---|
us |
api.logz.io |
eu |
api-eu.logz.io |
uk |
api-uk.logz.io |
au |
api-au.logz.io |
ca |
api-ca.logz.io |
Credentials
| Name | Description |
|---|---|
api_token |
Logz.io API token with search privileges (X-API-TOKEN header). |
Base Query Templates
Use ${variable} placeholders to scope log searches to a project automatically:
kubernetes.namespace_name:${project_slug} AND env:${environment}
Variables substituted at search time: project_slug, org_slug, team_slug, environment, project_id, project_type_slug (the first project type). Unknown variables are not checked at configuration time; the search fails when it expands them.
Filter Operators
| Operator | Translation |
|---|---|
eq |
Elasticsearch term |
ne |
Elasticsearch bool.must_not.term |
contains |
match_phrase on the configured message_field; non-leading wildcard (value*) on other fields |
starts_with |
Elasticsearch prefix |
regex |
Elasticsearch regexp (patterns starting with .*, *, or ? are rejected) |
Development
# Clone alongside imbi-common
git clone https://github.com/AWeber-Imbi/imbi-plugin-logzio
git clone https://github.com/AWeber-Imbi/imbi-common
cd imbi-plugin-logzio
UV_CONFIG_FILE=/dev/null uv sync
UV_CONFIG_FILE=/dev/null uv run pytest tests/
UV_CONFIG_FILE=/dev/null uv run coverage run -m pytest tests/ && uv run coverage report
Metadata
Release files for imbi-plugin-logzio 2.43.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| imbi_plugin_logzio-2.43.1.tar.gz | 18.3 kB | With provenance | Details for imbi_plugin_logzio-2.43.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| imbi_plugin_logzio-2.43.1-py3-none-any.whl | Python 3 | none | any | Details for imbi_plugin_logzio-2.43.1-py3-none-any.whl |
Total release size: 31.4 kB
Release files / imbi_plugin_logzio-2.43.1.tar.gz
| Download URL | imbi_plugin_logzio-2.43.1.tar.gz |
|---|---|
| Size | 18.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b366187d4d5a16ff50faa676e57f8c909073686bcc5bc1c347c62b4bd00cef69
|
|
BLAKE2b-256 checksum How to use checksums |
5de110235dc5be34a64ab9af159650681c89a5b23a911039dab43a4138c9db70
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 4, 2026.
Transparency logRelease files / imbi_plugin_logzio-2.43.1-py3-none-any.whl
| Download URL | imbi_plugin_logzio-2.43.1-py3-none-any.whl |
|---|---|
| Size | 13.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f8067ad727f6722ac224425922f9e283b0cf34e96038b28174323aa4c243a21f
|
|
BLAKE2b-256 checksum How to use checksums |
4cc89deb76e8ce92b0f9211d1a1b48799419dce2d8cddd648ab5f01acc2d9aa2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 4, 2026.
Transparency logSecurity for imbi-plugin-logzio 2.43.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for imbi_plugin_logzio-2.43.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 4, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
