[Uptime-UX] Added nav search keywords for uptime and user experience app

[shahzad31]

Summary

Fixes: elastic/uptime#256

Added nav search keywords for uptime and user experience app

User can search for uptime using following keywords

          'Synthetics',
          'pings',
          'checks',
          'availability',
          'response duration',
          'response time',
          'outside in',
          'reachability',
          'reachable',
          'digital',
          'performance',
          'web performance',
          'web perf',

and these deep links are also added

          { id: 'Down monitors', title: 'Down monitors', path: '/?statusFilter=down' },
          { id: 'Certificates', title: 'TLS Certificates', path: '/certificates' },
          { id: 'Settings', title: 'Settings', path: '/settings' },

User can search for UX app using following keywords

          'RUM',
          'Real User Monitoring',
          'DEM',
          'Digital Experience Monitoring',
          'EUM',
          'End User Monitoring',
          'UX',
          'Javascript',
          'APM',
          'Mobile',
          'digital',
          'performance',
          'web performance',
          'web perf',

Screenshots:

[elasticmachine]

Pinging @elastic/uptime (Team:uptime)

[elasticmachine]

Pinging @elastic/apm-ui (Team:apm)

[justinkambic]

Had one question on the code review.

[justinkambic]

"Digital" seems a little too general to me. Is there some UX-specific context to the term that I am missing?

cc @drewpost

[drewpost]

Generality was certainly what I was going for with this. With digital tied to so many things: digital performance, digital experience, digital transformation, I wanted to try and be general at the top of the funnel, so to speak, for discoverability reasons. cc @justinkambic

[justinkambic]

👍

[justinkambic]

Same comment regarding digital as the one I had in the UX keywords.

[drewpost]

Same as above:

Generality was certainly what I was going for with this. With digital tied to so many things: digital performance, digital experience, digital transformation, I wanted to try and be general at the top of the funnel, so to speak, for discoverability reasons. cc @justinkambic

[justinkambic]

Is @elastic/apm-ui ok with this?

[formgeist]

Seeing as the first result in the list will always be the APM app, I think we're OK with additionally showing a link to the UX app as well as a secondary option.

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 7f86246

Metrics [docs]

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
apm	22.9KB	23.1KB	+199.0B
uptime	19.3KB	19.7KB	+396.0B
total			+595.0B

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[justinkambic]

I don't have any further concerns. LGTM!

[sorenlouv]

Sorry @justinkambic. Not intentional - just fat fingers

[justinkambic]

Not intentional - just fat fingers

@sqren I was clearing GH notifications and came to this comment without any context. Initial reaction was "oh my.. how long has Søren been waiting for this review?" 🤣

[sorenlouv]

Not very long it turns out :D

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 90616 or prevent reminders by adding the backport:skip label.

[kibanamachine]

Backport result

{"level":"info","message":"POST https://api.github.com/graphql (status: 200)"}
{"level":"info","message":"POST https://api.github.com/graphql (status: 200)"}
{"meta":{"labels":["Team:apm","Team:uptime","auto-backport","backport missing","release_note:enhancement","v7.12.0","v8.0.0"],"branchLabelMapping":{"^v8.0.0$":"master","^v7.12.0$":"7.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"},"existingTargetPullRequests":[]},"level":"info","message":"Inputs when calculating target branches:"}
{"meta":["7.x"],"level":"info","message":"Target branches inferred from labels:"}
{"meta":{"killed":false,"code":2,"signal":null,"cmd":"git remote rm kibanamachine","stdout":"","stderr":"error: No such remote: 'kibanamachine'\n"},"level":"info","message":"exec error 'git remote rm kibanamachine':"}
{"meta":{"killed":false,"code":2,"signal":null,"cmd":"git remote rm elastic","stdout":"","stderr":"error: No such remote: 'elastic'\n"},"level":"info","message":"exec error 'git remote rm elastic':"}
{"level":"info","message":"Backporting [{\"sourceBranch\":\"master\",\"targetBranchesFromLabels\":[\"7.x\"],\"sha\":\"08111e40d32583382ae6e6a300f014cef7d18eba\",\"formattedMessage\":\"[Uptime-UX] Added nav search keywords for uptime and user experience app (#90616)\",\"originalMessage\":\"[Uptime-UX] Added nav search keywords for uptime and user experience app (#90616)\",\"pullNumber\":90616,\"existingTargetPullRequests\":[]}] to 7.x"}

Backporting to 7.x:
{"level":"info","message":"Backporting via filesystem"}
{"level":"info","message":"Creating PR with title: \"[7.x] [Uptime-UX] Added nav search keywords for uptime and user experience app (#90616)\". kibanamachine:backport/7.x/pr-90616 -> 7.x"}
{"level":"info","message":"POST /repos/elastic/kibana/pulls - 201 in 956ms"}
{"level":"info","message":"Adding assignees to #91268: shahzad31"}
{"level":"info","message":"POST /repos/elastic/kibana/issues/91268/assignees - 201 in 558ms"}
{"level":"info","message":"Adding labels: backport"}
{"level":"info","message":"POST /repos/elastic/kibana/issues/91268/labels - 200 in 401ms"}
View pull request: https://github.com/elastic/kibana/pull/91268