This project has been archived by its maintainers, and is no longer receiving any updates.
ISIS-specific Kafka tools. Deserialises the ESS flatbuffers blobs from Kafka.
Also allows replaying data in a topic.
Usage
To run the latest version, install uv and use uvx saluki <args>.
alternatively you can pip install saluki and run it from a venv.
See saluki --help for all options.
listen - Listen to a topic for updates
saluki listen mybroker:9092/mytopic - This will listen for updates for mytopic on mybroker.
Filter to specific schemas
saluki listen mybroker:9092/mytopic -f f144 -f f142 - This will listen for updates but ignore messages with schema IDs of f142 or f144
consume- Consume from a topic
saluki consume mybroker:9092/mytopic -p 1 -o 123456 -m 10 - This will print 9 messages before (and inclusively the offset specified) offset 123456 of mytopic on mybroker, in partition 1.
Use the -g flag to go the other way, ie. in the above example to consume the 9 messages after offset 123456
You can also filter out messages to specific schema(s) with the -f flag, like the example above for listen.
sniff - List all topics and their high, low watermarks and number of messages
saluki sniff mybroker:9092
Output looks as follows:
$ saluki sniff mybroker:9092
INFO:saluki:Cluster ID: redpanda.0faa4595-7298-407e-9db7-7e2758d1af1f
INFO:saluki:Brokers:
INFO:saluki: 192.168.0.111:9092/1
INFO:saluki: 192.168.0.112:9092/2
INFO:saluki: 192.168.0.113:9092/0
INFO:saluki:Topics:
INFO:saluki: MERLIN_events:
INFO:saluki: 0 - low:262322729, high:302663378, num_messages:40340649
INFO:saluki: MERLIN_runInfo:
INFO:saluki: 0 - low:335, high:2516, num_messages:2181
INFO:saluki: MERLIN_monitorHistograms:
INFO:saluki: 0 - low:7515, high:7551, num_messages:36
play - Replay data from one topic to another
Between offsets
saluki play mybroker:9092/source_topic mybroker:9092/dest_topic -o 123 125 - This will forward messages at offset 123, 124 and 125 in the source_topic to the dest_topic
Between timestamps
saluki play mybroker:9092/source_topic mybroker:9092/dest_topic -t 1762209990 1762209992 - This will forward messages between the two given timestamps.
Developer setup
pip install -e .[dev]
Metadata
Release files for saluki 0.0.5
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 | |
|---|---|---|---|---|
| saluki-0.0.5.tar.gz | 94.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| saluki-0.0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 105.3 kB
Release files / saluki-0.0.5.tar.gz
| Download URL | saluki-0.0.5.tar.gz |
|---|---|
| Size | 94.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
763425c991bebea760071f78e4ba0321bbfdfb9f47ea1096dc63b6b242b5ff19
|
|
BLAKE2b-256 checksum How to use checksums |
71a44e545bd3ce010dbd398ce7b878249bc2cd5beeb96c008509a8835e2ba35c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Dec 4, 2025.
Transparency logRelease files / saluki-0.0.5-py3-none-any.whl
| Download URL | saluki-0.0.5-py3-none-any.whl |
|---|---|
| Size | 10.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
46a1fdfae01b0776a9ad82bcf7ba1d6cd9f1c8bdc9ec6363247766a7e0e9c4f9
|
|
BLAKE2b-256 checksum How to use checksums |
b4aaa4feef62bd0890b81165fe6cb4969822e93b3e13608fab7ca7ef3bf3540f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Dec 4, 2025.
Transparency logSecurity for saluki 0.0.5
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for saluki-0.0.5.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 Dec 4, 2025.
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.