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

[APM] Adds 7.x migration message to 'no services' view #30811

Conversation

jasonrhodes
Copy link
Member

@jasonrhodes jasonrhodes commented Feb 12, 2019

Closes #30274 (need to move APM server check/copy update from that ticket into separate ticket)

Summary

Adds a new message to the APM services list when no data is found, encouraging users who are upgrading from pre-7.x versions to upgrade APM server and possibly migrate data.

NOTE: Still need to track down the "Kibana Migration Assistant" link path....

screen shot 2019-02-12 at 7 29 48 am

@jasonrhodes jasonrhodes requested a review from a team as a code owner February 12, 2019 12:40
@jasonrhodes jasonrhodes requested review from formgeist, sorenlouv and makwarth and removed request for formgeist February 12, 2019 12:40
'You may also have old data that needs to be migrated.'
})}{' '}
{/* TODO: GET REAL URL FOR KIBANA MIGRATION ASSISTANT */}
<KibanaLink pathname="/app/kibana" hash="/management">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is the url: /app/kibana#/management/elasticsearch/upgrade_assistant.
Unfortunately we cannot link to the "Indices" tab: #29845

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm I saw that in the management section but it says 8.0 Upgrade Assistant even when I'm on the 7.0 branch ... I'm not sure who to confirm this with

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tylersmalley would be the one to ask.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmed with the operations team that this is the correct URL. Will remove that comment and push.

@jasonrhodes
Copy link
Member Author

Made some review tweaks and added a test for the new component. Will check with @tylersmalley about the migration assistant link.

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

describe('No Services Message', () => {
it('should render correctly when historical data is found', () => {
const wrapper = shallow(<NoServicesMessage historicalDataFound={true} />);
expect(wrapper).toMatchSnapshot();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is fine for now, but I think it would be great with a discussion about how we use snapshot.
I think we over-use them a bit. In this case, if the output changes the slightest the test will fail - which causes noise, and it's easy to overlook if something significant actually changed.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we probably need to write up a clear guide on how we want to do testing and what kinds of testing we want to do in what situations, so that we can refer to it as we develop.

expect(wrapper).toMatchSnapshot();
});

it('should render correctly when NO historical data is found', () => {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about should show link to Getting Started guide, when no historical data is found

import { NoServicesMessage } from '../NoServicesMessage';

describe('No Services Message', () => {
it('should render correctly when historical data is found', () => {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about: should show "no services"-message when historical data was found

import React from 'react';
import { NoServicesMessage } from '../NoServicesMessage';

describe('No Services Message', () => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are these spaces intentional or is it supposed to be the component name (NoServicesMessage)?

@jasonrhodes
Copy link
Member Author

retest

@tylersmalley
Copy link
Contributor

There were comments throughout, but just a follow-up /app/kibana#/management/elasticsearch/upgrade_assistant is the correct link. In 7.x, the Upgrade Assistant is technically called the "8.0 Upgrade Assistant" as it's to assist users with their upgrade to the next major version. It just also happens to be the place where we assist users with these APM indices for the current version.

@jasonrhodes
Copy link
Member Author

retest

@LeeDr LeeDr added Team:APM All issues that need APM UI Team support and removed Team:APM All issues that need APM UI Team support labels Feb 12, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/apm-ui

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@jasonrhodes jasonrhodes merged commit 19cbb23 into elastic:master Feb 13, 2019
@jasonrhodes jasonrhodes deleted the 7.0-migration-messaging/apm-30274-master-cherry branch February 13, 2019 12:16
jasonrhodes added a commit to jasonrhodes/kibana that referenced this pull request Feb 13, 2019
* Adds 7.x migration message to 'no services message'

* Small tweaks and adds a test

* Removed comment after confirming link url with operations team

* Updates test descriptions to be more descriptive per review
jasonrhodes added a commit to jasonrhodes/kibana that referenced this pull request Feb 13, 2019
* Adds 7.x migration message to 'no services message'

* Small tweaks and adds a test

* Removed comment after confirming link url with operations team

* Updates test descriptions to be more descriptive per review
jasonrhodes added a commit that referenced this pull request Feb 14, 2019
* Adds 7.x migration message to 'no services message'

* Small tweaks and adds a test

* Removed comment after confirming link url with operations team

* Updates test descriptions to be more descriptive per review
jasonrhodes added a commit that referenced this pull request Feb 14, 2019
* Adds 7.x migration message to 'no services message'

* Small tweaks and adds a test

* Removed comment after confirming link url with operations team

* Updates test descriptions to be more descriptive per review
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:APM All issues that need APM UI Team support
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants