log_ctrl
log_ctrl is a package for accessing log files stored in a specified
log directory over a network using grpc_frame.
It does not add log retrieval RPCs to the DeviceServer or application
that writes the logs. log_ctrl runs as an independent, read-only gRPC
server that accesses existing log files.
application / DeviceServer
│
│ write
▼
C:\opt\ese774\log
├── cobotta4_server.log
├── cobotta4_server.log.2026-04-06
├── cobotta4_server2.log
└── cobotta4_server2.log.2026-06-16
▲
│ read only
│
LogCtrl
│
▼
log gRPC server
│
▼
DeviceProxy("log", ...)
Log names
In log_ctrl, the part before .log is called the log_name.
cobotta4_server.log
^^^^^^^^^^^^^^^
log_name
Rotated log files use the following format:
<log_name>.log.YYYY-MM-DD
The log_name does not need to match the DeviceServer name or device
class name. log_ctrl uses the log_name exactly as it appears in the
filename.
Main features
log_names(): Get the list oflog_namevalues from existing log files.dates(log_name): Get the list of rotation dates for the specifiedlog_name.exists(log_name, date=None): Check whether the current log or a log for a specified date exists.tail(log_name, lines=100, date=None): Get the end of a log as a string.raw_files(): List all files under the log directory as relative paths.read(log_name, date=None): Read a log file asbytes.read_raw(relative_path): Read an arbitrary file confirmed byraw_files()asbytes.
Large log files are transferred in chunks using grpc_frame
StreamCall. Client-side code does not need to handle the stream
directly; read() and read_raw() join the received chunks and return
them as bytes.
Installation
Install in an environment where grpc_frame is available.
python -m pip install .
For development, use an editable install:
python -m pip install -e .
Starting LogServer
from log_ctrl.server_grpc import log_grpc_server
GRPC_HOST = "0.0.0.0"
GRPC_PORT = 50060
LOG_DIR = r"C:\opt\ese774\log"
log_grpc_server(
grpc_host=GRPC_HOST,
grpc_port=GRPC_PORT,
log_dir=LOG_DIR,
)
If logger is omitted, the standard logging module is used. To use an
existing logger, pass it with logger=.
Client
Use DeviceProxy as the transparent grpc_frame client.
from log_ctrl.server_grpc import DeviceProxy
client = DeviceProxy(
"log",
server_ip="127.0.0.1",
server_port=50060,
set_timeout_sec=10.0,
async_mode=False,
)
try:
log_names = client.log_names()
print(log_names)
if len(log_names) > 0:
log_name = log_names[0]
print(client.dates(log_name))
if client.exists(log_name):
data = client.read(log_name)
print(len(data))
finally:
client.close()
The names returned by log_names() are not limited to names for which a
current <log_name>.log file exists. A name is also included when only
rotated log files remain. Check exists(log_name) as needed before
reading the current log.
API
client.log_names()
client.dates(log_name)
client.exists(log_name)
client.exists(log_name, date="2026-04-06")
client.tail(log_name, lines=100)
client.tail(log_name, lines=100, date="2026-04-06")
client.raw_files()
client.read(log_name)
client.read(log_name, date="2026-04-06")
client.read_raw("cobotta4_server.log.2026-04-06")
read() and read_raw() return bytes. To handle a log as text,
decode it on the client using the appropriate character encoding.
text = client.read(log_name).decode("utf-8")
tail() is decoded on the server using the configured encoding and
returns str.
Documentation
Sphinx documentation is available under docs/.
docs/index.mddocs/quickstart.mddocs/usage.mddocs/rotation.mddocs/architecture.md
License
See LICENSE.
Metadata
Release files for log-ctrl 0.0.4
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 | |
|---|---|---|---|---|
| log_ctrl-0.0.4.tar.gz | 18.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| log_ctrl-0.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 35.5 kB
Release files / log_ctrl-0.0.4.tar.gz
| Download URL | log_ctrl-0.0.4.tar.gz |
|---|---|
| Size | 18.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d898804766eb6d32530d22c65f6db15a76cbf5fa4533d6d77810a28742fa7f0f
|
|
BLAKE2b-256 checksum How to use checksums |
a453dd873267bb5b4b729dc40253b9bbaba03046a36aeb23d93ac29c38290638
|
| 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 Oct 24, 2026.
Transparency logRelease files / log_ctrl-0.0.4-py3-none-any.whl
| Download URL | log_ctrl-0.0.4-py3-none-any.whl |
|---|---|
| Size | 17.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f74358422a7bb1f2d27a0f3627291b1048b84f0b21833e1c85df9aaf66f868f6
|
|
BLAKE2b-256 checksum How to use checksums |
cfc3d16cd9cceb8e4a9e472ad8307c68e55eeaefd3d35ecc820efb79fc953958
|
| 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 Oct 24, 2026.
Transparency logSecurity for log-ctrl 0.0.4
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 log_ctrl-0.0.4.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 Oct 24, 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.