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] Remote Agent Config: Add additional (java) options #59860

Merged

Conversation

sorenlouv
Copy link
Member

@sorenlouv sorenlouv commented Mar 11, 2020

Closes: elastic/apm#214

TODO:

  • Agent specific options (only show option for specific services)
  • When selecting "All" services, only show options that are relevant to all backend agents (not considering RUM)
  • Highlight "Agent configuration" menu item when creating/editing config
  • Options are sorted alphabetically
  • Limit options by to specific agents (eg java specific options)
  • Discard button on settings page should reset settings
  • Cancel button on service page should take user to the list page (overview)
  • Bottom bar overflows the left hand navigation (waiting for EUI to add a prop, or allow arbitrary css) (Interoperability of EuiBottomBar and EuiNavDrawer eui#3146)
  • Review page (not for 7.7)
  • Config per agent name (not for 7.7)
  • Categories: list options under categories (not for 7.7)
  • Highlight previously edited options (not for 7.7)

Questions:

  • Are the descriptions the same across all agents?
  • Are the default values the same across all agents?

image

image

image

image

@sorenlouv sorenlouv marked this pull request as ready for review March 11, 2020 15:05
@sorenlouv sorenlouv requested a review from a team as a code owner March 11, 2020 15:05
),
name: RouteName.AGENT_CONFIGURATION_CREATE,
component: () => {
const { search } = history.location;
Copy link
Member Author

@sorenlouv sorenlouv Mar 11, 2020

Choose a reason for hiding this comment

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

Controversy #1: retrieving search from history singleton. Everywhere else we get it from useLocation hook.
The problem with hooks is that they only work inside react components (not vanilla js) so in general I think when given the choice it's better to use the singleton approach (for consistency).

afact there are no difference between the two approaches. LMK if there are!

return (
<EuiFieldNumber
placeholder={setting.placeholder || defaultInputPlaceholder}
value={(value as any) || ''}
Copy link
Member Author

Choose a reason for hiding this comment

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

EuiFieldNumber currently don't accept strings. This will change with this PR

@sorenlouv sorenlouv force-pushed the agent-configuration-additional-settings branch 2 times, most recently from b8cab16 to 44f18c8 Compare March 16, 2020 09:20
sorenlouv and others added 12 commits March 22, 2020 09:02
…Configurations/AgentConfigurationCreateEdit/ServicePage/ServicePage.tsx

Co-Authored-By: Casper Hübertz <casper@formgeist.com>
…Configurations/AgentConfigurationCreateEdit/ServicePage/ServicePage.tsx

Co-Authored-By: Casper Hübertz <casper@formgeist.com>
…Configurations/AgentConfigurationCreateEdit/ServicePage/ServicePage.tsx

Co-Authored-By: Casper Hübertz <casper@formgeist.com>
@sorenlouv sorenlouv force-pushed the agent-configuration-additional-settings branch from cc73feb to cb51fcc Compare March 22, 2020 08:05
@sorenlouv
Copy link
Member Author

If you have unsaved changes (which is the current behaviour), wouldn't it make more sense to cancel the edits and return to the create page where you started instead of sending the user back to the list page?

@formgeist

I'll change the Cancel button to be a Discard button while in edit mode. It will behave as described above.

WDYT should happen when creating a new config?

@formgeist
Copy link
Contributor

WDYT should happen when creating a new config?

If we're keeping the "discard" changes button even on a new config, the user would have to go back to the overview page via the sidenav to "cancel", as there's no specified cancel option. I don't think that's too big of an issue.

Copy link
Contributor

@cauemarcondes cauemarcondes left a comment

Choose a reason for hiding this comment

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

LGTM 👍🏻

@kibanamachine
Copy link
Contributor

💚 Build Succeeded

History

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[APM] Remote agent configuration: Update flyouts to feature new config options
8 participants