Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Spike] Enhance Entity Relationships - AWS_ELASTICSEARCH_CLUSTER #1925

Open
kford-newrelic opened this issue Jun 4, 2024 · 2 comments
Open
Assignees
Labels
2 Story Point Estimate jul-sep qtr Represents proposed work item for the Jul-Sep quarter spike Research spike. Technical solution needing discovery

Comments

@kford-newrelic
Copy link
Contributor

Description

Cross team collaborative efforts to capture, emit and process needed data for supporting AWS service entity relationships

For Q2, the Java Agent Team will take the lead on researching, coding and testing the emitting of sufficient data for Elasticsearch clusters, so that entity relationships can be created

Acceptance Criteria

Research spike. Get familiar with the AWS service and understand what it means for an APM application to use it. Further break down subsequent work to be done once better understood.

Design Consideration/Limitations

N/A

Dependencies

N/A

Additional context

N/A

@workato-integration
Copy link

@kford-newrelic kford-newrelic added spike Research spike. Technical solution needing discovery jul-sep qtr Represents proposed work item for the Jul-Sep quarter labels Jun 4, 2024
@kford-newrelic kford-newrelic added the 2 Story Point Estimate label Jun 7, 2024
@kford-newrelic kford-newrelic moved this to In Quarter in Java Engineering Board Jun 28, 2024
@obenkenobi obenkenobi removed their assignment Aug 20, 2024
@jbedell-newrelic jbedell-newrelic self-assigned this Aug 21, 2024
@jbedell-newrelic jbedell-newrelic moved this from In Quarter to In Sprint in Java Engineering Board Aug 21, 2024
@kford-newrelic kford-newrelic moved this from In Sprint to In Quarter in Java Engineering Board Sep 11, 2024
@github-project-automation github-project-automation bot moved this from In Sprint to Code Complete/Done in Java Engineering Board Dec 13, 2024
@jbedell-newrelic jbedell-newrelic moved this from Code Complete/Done to In Sprint in Java Engineering Board Dec 13, 2024
@github-project-automation github-project-automation bot moved this from In Sprint to Triage in Java Engineering Board Dec 13, 2024
@jbedell-newrelic jbedell-newrelic moved this from Triage to In Sprint in Java Engineering Board Dec 13, 2024
@workato-integration
Copy link

Work has been completed on this issue.

@github-project-automation github-project-automation bot moved this from In Sprint to Code Complete/Done in Java Engineering Board Dec 13, 2024
@workato-integration workato-integration bot reopened this Dec 16, 2024
@github-project-automation github-project-automation bot moved this from Code Complete/Done to Triage in Java Engineering Board Dec 16, 2024
@jbedell-newrelic jbedell-newrelic moved this from Triage to In Sprint in Java Engineering Board Dec 16, 2024
@kmudduluru kmudduluru moved this from In Sprint to In Quarter in Java Engineering Board Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 Story Point Estimate jul-sep qtr Represents proposed work item for the Jul-Sep quarter spike Research spike. Technical solution needing discovery
Projects
Status: In Quarter
Development

No branches or pull requests

3 participants