jfrog / jfrog/log-analytics-datadog
Telemetry from Curation, Advanced Security & Xray
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 8
- Forks
- 6
- Avg merge
- 4h 15m
- Merged PRs (30d)
- 1
Description
Customer would like to be able to report on and react to Curation Events, such as blocked package pending update, using DataDog. Many of the curation blocking events created by service accounts, and not people. We're looking at ways of making sure people can easily discover why their CI Pipeline failed when Curation blocked a package.
Contributor guide
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 describes reporting and reacting to Curation Events in DataDog, especially events created by service accounts when packages are blocked. No files, tests, or entry points are mentioned; begin by locating the existing Curation, Advanced Security, Xray, and CI Pipeline integration points, then define the telemetry and discovery behavior that would satisfy the request.
Written by the indexing model from the issue text.
Assessment
- Domain
- observability, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100