The agent2query framework is aiming to provide E2E testing capabilities for different NewRelic integrations and/or components. These tests are meant to cover the telemetry (MELT) we process throughout the data processing pipelines and alert of potential issues so that they are tackled as soon as we can. We are currently moving forward from a POC to an actual product, and thus, we need to have meaningful use cases under test. The way the framework works is simple:
We have a test app running with the NR integration we want to test
We have some synthetic jobs executing periodic requests to generate predictable telemetry (MELT)
We define some tests and execute them periodically to verify that the predictable telemetry has been processed in the exact way we expected
The tests we execute consist in performing a query to Dirac using NerdGraph and perform assertions on the response. This data is important as it represents what the customer sees, and is the same data used to populate our dashboards.
This is a discovery spike, to get familiar with the testing framework, how it works and how to write tests and enhance it. New issues for specific tests should then be created and actioned.
Acceptance Criteria
Discovery spike. Intention is to get familiar with the service, how it works, identify new tests to be implemented and create issues for those.
Design Consideration/Limitations
N/A
Dependencies
N/A
Additional context
Additional context can be found in the original work request (NR-280331)
workato-integration[bot]
commented
2 weeks ago
Description
The agent2query framework is aiming to provide E2E testing capabilities for different NewRelic integrations and/or components. These tests are meant to cover the telemetry (MELT) we process throughout the data processing pipelines and alert of potential issues so that they are tackled as soon as we can. We are currently moving forward from a POC to an actual product, and thus, we need to have meaningful use cases under test. The way the framework works is simple:
The tests we execute consist in performing a query to Dirac using NerdGraph and perform assertions on the response. This data is important as it represents what the customer sees, and is the same data used to populate our dashboards.
This is a discovery spike, to get familiar with the testing framework, how it works and how to write tests and enhance it. New issues for specific tests should then be created and actioned.
Acceptance Criteria
Discovery spike. Intention is to get familiar with the service, how it works, identify new tests to be implemented and create issues for those.
Design Consideration/Limitations
N/A
Dependencies
N/A
Additional context
Additional context can be found in the original work request (NR-280331)