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] Research how to answer questions around library, agent, and node versions #2132

Closed
bizob2828 opened this issue Apr 9, 2024 · 5 comments
Assignees
Labels
points: 5 1-2 weeks

Comments

@bizob2828
Copy link
Member

Description

Our metric collection around library usage is rigid. We cannot answer the following questions easily:

  • Which agent version is a customer using with a specific 3rd party library version?
  • Which OS is a customer using with a specific agent version?
  • Which OS is a customer using with a specific 3rd party library version?
  • Which account is using a specific 3rd party library version?

Acceptance Criteria

Research how to answer the questions above. There are probably more questions we want to answer as well. We have access to a system called BDMS but we need to figure out if there's any work needed to make these queries.

@workato-integration
Copy link

@newrelic-node-agent-team newrelic-node-agent-team added this to Triage Needed: Unprioritized Features in Node.js Engineering Board Apr 9, 2024
@jsumners-nr
Copy link
Contributor

I look forward to us being able to answer these questions. I am very surprised we cannot do so already.

@kmudduluru kmudduluru added points: 5 1-2 weeks and removed needs-triage labels Apr 9, 2024
@kmudduluru kmudduluru moved this from Triage Needed: Unprioritized Features to To do: Features here are prioritized for this sprint in Node.js Engineering Board Apr 30, 2024
@jsumners-nr
Copy link
Contributor

Here's what I have found in regard to this issue:

  1. The "BMDS" (Basic Metadata Service) is a Java application that receives events and stores the information in a table.
  2. The BMDS app has a list of modules to recognize in event data so that information about them can be stored in the table. This is a hard coded list that must be updated by an engineer for any modules we are interested in querying.
  3. There is a traditional DBMS table that contains the raw information from the events that we could query, but we need to request access to the read replica in order to determine if this would solve our needs.
  4. The APM Services team has started researching a project that would make the data in 3 much easier to query and would store the data in NRDB. We should express support for this initiative.

@jsumners-nr jsumners-nr self-assigned this May 17, 2024
@jsumners-nr jsumners-nr moved this from To do: Features here are prioritized for this sprint (jira for remaining tickets) to In progress: Issues being worked on in Node.js Engineering Board May 17, 2024
@bizob2828
Copy link
Member Author

bizob2828 commented May 20, 2024

@jsumners-nr are you suggesting we wait for the APM services team to do their research and we can build queries to make dashboards? If so, can you link that work here so we can track it?

@jsumners-nr
Copy link
Contributor

Node.js Engineering Board automation moved this from In progress: Issues being worked on to Done: Issues recently completed Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
points: 5 1-2 weeks
Projects
Node.js Engineering Board
  
Done: Issues recently completed
Development

No branches or pull requests

3 participants