Repository navigation
[APM] Performance comparison charts by user agent (browser) - #49582
Conversation
💔 Build Failed
|
1f07d81 to
71be5ce
Compare
💔 Build Failed
|
71be5ce to
44d676a
Compare
💔 Build Failed
|
2f1410f to
2a1ae9e
Compare
💔 Build Failed
|
2a1ae9e to
dfa8e2a
Compare
💔 Build Failed
|
|
@elasticmachine retest |
|
@elasticmachine test this please |
💚 Build Succeeded
|
|
In order to test multiple values or lines, we would need to fake a dataset that has some other values than |
|
I created a Codesandbox app with RUM agent installed: https://codesandbox.io/s/admiring-mclaren-6o624 then pointed it at my cloud cluster, deployed it with netlify, then pointed my local kibana at that cluster, then loaded the page in a bunch of different browsers. It would be nicer to have a more realistic data set, but I think we should spend the time on that once we work on adding sample data. |
|
@elasticmachine merge upstream |
1 similar comment
|
@elasticmachine merge upstream |
💔 Build Failed
|
6020cfd to
d6d7539
Compare
💚 Build Succeeded
|
There was a problem hiding this comment.
This test is... not great. And it's totally on me (I introduced it!).
LMK if you have any ideas to improve it.
There was a problem hiding this comment.
Actually, it would be useful if you added a user agent in the sample doc:
There was a problem hiding this comment.
Added user agent in c39defa8e1.
There was a problem hiding this comment.
Missing rebase, or should this go into ?
kibana/x-pack/legacy/plugins/apm/common/transaction_types.ts
Lines 7 to 9 in 51a6eeb
There was a problem hiding this comment.
fyi @cauemarcondes: this will probably conflict with your changes in #49638
There was a problem hiding this comment.
These colors are defined several times already. Perhaps it would make sense to add them as a constant in https://github.com/elastic/kibana/tree/c40b32010462aa6731d5c8a9312444228b3a819e/x-pack/legacy/plugins/apm/common
Btw. I like the modulus approach (colors[index % colors.length]) you took that ensures we'll loop through them regardless how many lines there are. In contrast to
So maybe a shared helper together with the colors would make sense?
const getVizColorForIndex = index => vizColors[index % vizColors.length]There was a problem hiding this comment.
Added this in e865ebe1b5.
There was a problem hiding this comment.
@smith if you rebase master, you'll have to replace getTimeFormatter to getDurationFormatter
d6d7539 to
e865ebe
Compare
💔 Build Failed
|
💔 Build Failed
|
14f721b to
a137078
Compare
💔 Build Failed
|
There was a problem hiding this comment.
A file with request type constants was recently added:
kibana/x-pack/legacy/plugins/apm/common/transaction_types.ts
Lines 6 to 9 in 4c33f2a
a137078 to
0b3ca10
Compare
💚 Build Succeeded
|
Show a chart with average page load broken down by user agent name on the RUM overview. I tested this by setting up a RUM agent on a sample app on my test cloud cluster. On the internal APM dev cluster you'll need to set the time range to about 90 days then look at the "client" app and find the time range where there are requests. Unfortunately with this sample data the only series you see is "Other" because there aren't a lot of requests. Fixes elastic#43342
0b3ca10 to
508454a
Compare
💚 Build Succeeded |
…49582) Show a chart with average page load broken down by user agent name on the RUM overview. I tested this by setting up a RUM agent on a sample app on my test cloud cluster. On the internal APM dev cluster you'll need to set the time range to about 90 days then look at the "client" app and find the time range where there are requests. Unfortunately with this sample data the only series you see is "Other" because there aren't a lot of requests. Also factor out the color selection into a common helper. Fixes elastic#43342
…49582) Show a chart with average page load broken down by user agent name on the RUM overview. I tested this by setting up a RUM agent on a sample app on my test cloud cluster. On the internal APM dev cluster you'll need to set the time range to about 90 days then look at the "client" app and find the time range where there are requests. Unfortunately with this sample data the only series you see is "Other" because there aren't a lot of requests. Also factor out the color selection into a common helper. Fixes elastic#43342
Show a chart with average page load broken down by user agent name on the RUM overview.
I tested this by setting up a RUM agent on a sample app on my test cloud cluster.
On the internal APM dev cluster you'll need to set the time range to about 90 days then look at the "client" app and find the time range where there are requests. Unfortunately with this sample data the only series you see is "Other" because there aren't a lot of requests.
Also factor out the color selection into a common helper.
Fixes #43342