Skip to content

[proposal] Live HTTP Log Streaming Support (like azure kudu logstream) #802

@pippistro-fedro

Description

@pippistro-fedro

Proposal: Live HTTP Log Streaming Support (working implementation available)

Summary

klogg currently allows opening a URL, which effectively results in downloading a remote file and displaying it locally.

I’d like to propose adding native support for live HTTP log streaming, allowing klogg to consume and display streaming endpoints such as those exposed by Azure WebApps via Kudu SCM.

A working implementation is already available on my fork.

Motivation / Use case

Several platforms (notably cloud services) expose logs via long-lived HTTP streams rather than static files.
A concrete example is Azure WebApps log streaming via Kudu SCM, which today requires external tools or browsers.

Native support in klogg would allow:

  • real-time log inspection
  • reuse of existing filtering/search capabilities
  • no need for temporary external tooling

Implementation overview (already implemented and working)

I have already implemented and tested this feature on my fork, in branch logstream: https://github.com/pippistro-fedro/klogg/tree/logstream

The implementation introduces:

  • Custom HTTP headers support
    • Basic Authentication support
    • Generic editable input to manually add any additional HTTP headers
  • “Live” HTTP request mode
    • When enabled, the HTTP response body is continuously appended to a temporary file as data arrives from the stream
  • Standard klogg file visualization
    • The temporary file is displayed using existing klogg views and features
  • Extended Favorites
    • Favorites have been extended to support both:
      • traditional files
      • complex objects such as an HTTP log stream configuration (URL, headers, live flag, etc.)

Current status

  • Feature implemented
  • Working and tested against Azure Kudu log streaming
  • Isolated in a dedicated branch (logstream)
  • No changes merged yet

Next steps

If this approach aligns with the project’s direction:

  • I can clean up the branch if needed
  • I’m happy to open a Pull Request and address review feedback

I may not be able to provide long-term maintenance, but I’m glad to help with follow-up adjustments related to the initial review.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions