opendevstack / opendevstack/ods-core
Observability for Ansible Playbooks
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 53
- Forks
- 34
- Avg merge
- 3h 26m
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
The current challenge is the lack of a comprehensive monitoring and alerting system for complex Ansible playbooks, which requires a mechanism to observe, trace, and provide a detailed view of the entire process from start to finish.
Describe the solution you'd like
Automate the installation of the OpenTelemetry Collector on OpenShift using a Helm chart. This chart should include a sample configuration to collect telemetry data from our Ansible scripts and send it an endpoint using the Opentelemetry Protocol (OTLP).
Describe alternatives you've considered
N/A
Additional context
N/A
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or existing entry points. Start by locating the OpenShift Helm chart and the Ansible scripts, then define a sample OpenTelemetry Collector configuration that sends their telemetry through OTLP; done means the collector installs successfully and the end-to-end telemetry flow is demonstrated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, helm
- Domain
- devops, infrastructure, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100