-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[APM] Remove rate aggregations #112343
[APM] Remove rate aggregations #112343
Conversation
Pinging @elastic/apm-ui (Team:apm) |
@elasticmachine merge upstream |
x-pack/plugins/apm/public/components/app/service_overview/service_overview_throughput_chart.tsx
Outdated
Show resolved
Hide resolved
jenkins, retest this please |
@elasticmachine merge upstream |
x-pack/plugins/apm/server/lib/backends/get_throughput_charts_for_backend.ts
Outdated
Show resolved
Hide resolved
x-pack/plugins/apm/server/lib/observability_overview/get_transactions_per_minute.ts
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a little worried about the bug I found. If it is indeed a bug it proves that we still don't have adequate test coverage.
We might want to pause this PR until we have synthetic data. This means that we need to postpone this for 7.16.
'apm_8.0.0': { | ||
start: '2021-08-03T06:50:15.910Z', | ||
end: '2021-08-03T07:20:15.910Z', | ||
}, | ||
'apm_data_generation_8.0.0': { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we find a less generic name than "apm_data_generation", eg "apm_synthetic_8.0.0"
While doing that, perhaps we can rename "apm_8.0.0" to "apm_opbeans_8.0.0"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, I can change it, I'll first look into the bug you've mentioned here #112343 (comment)
import archives_metadata from '../../common/fixtures/es_archiver/archives_metadata'; | ||
import { FtrProviderContext } from '../../common/ftr_provider_context'; | ||
import { registry } from '../../common/registry'; | ||
import { createApmApiSupertest } from '../../common/apm_api_supertest'; | ||
|
||
type ThroughputReturn = APIReturnType<'GET /api/apm/services/{serviceName}/throughput'>; | ||
|
||
export default function ApiTest({ getService }: FtrProviderContext) { | ||
const apmApiSupertest = createApmApiSupertest(getService('supertest')); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like the old syntax.
const apmApiClient = getService('apmApiClient');
and then
const response = await apmApiClient.readUser({...})
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This branch is based on 7.15
which is why the old syntax is still being used.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah, okay. I'm not sure it's worth backporting to 7.15 at this point tbh.
import { roundNumber } from '../../utils'; | ||
|
||
export default function ApiTest({ getService }: FtrProviderContext) { | ||
const apmApiSupertest = createApmApiSupertest(getService('supertest')); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use the new service
const apmApiSupertest = createApmApiSupertest(getService('supertest')); | |
const apmApiClient = getService('apmApiClient'); |
x-pack/plugins/apm/server/lib/backends/get_throughput_charts_for_backend.ts
Outdated
Show resolved
Hide resolved
Should this be for 7.x and not 7.15? |
💚 Build Succeeded
Metrics [docs]Public APIs missing comments
Async chunks
Public APIs missing exports
Page load bundle
History
To update your PR or re-run it, just comment with: |
it('has the correct throughput in tpm', () => { | ||
expectSnapshot(throughputResponse).toMatch(); | ||
expectSnapshot(throughputResponse.throughputUnit).toMatchInline(`"second"`); | ||
it('has same mea value for both periods', () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it('has same mea value for both periods', () => { | |
it('has same mean value for both periods', () => { |
closes #112240
Remove rate aggs and calculate throughput manually.
Before:
After: