Non-docker deployment option for custom OTel collector

Open
#241 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker
Domain
observability-sre

Research direction

Start by reviewing issue #142 and the repository's references to the custom OTel collector and its container image. Determine whether the collector source or downloadable binary is intended to be published; done would require a maintainer decision and a supported non-container distribution path.

Written by the indexing model from the issue text.

Description

enhancement

Is the OTel collector binary available for download without a container image or are there any plans for providing it in the future?

I'm assuming the answer is "no" to the first part of the question as the container image is all I could find and also from the fact that the custom collector source code and repo is not public (issue #142 ), but would like to know if there are any discussions to publish the repo and allow for alternative deployments.

Thanks.

Dominant language
Python
Stars
106
Forks
43
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from f5devcentral/application-study-tool

All issues in f5devcentral/application-study-tool

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.