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

[Ingest Manager] New Agent configuration doesn't start at Rev 1 #71774

Closed
mostlyjason opened this issue Jul 14, 2020 · 3 comments · Fixed by #72270
Closed

[Ingest Manager] New Agent configuration doesn't start at Rev 1 #71774

mostlyjason opened this issue Jul 14, 2020 · 3 comments · Fixed by #72270
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@mostlyjason
Copy link
Contributor

mostlyjason commented Jul 14, 2020

Kibana version:
8.0 snapshot

Describe the bug:
After creating a new Agent configuration it appears to start at rev 2.

Steps to reproduce:

  1. Add a new Agent configuration in Ingest Manager
  2. View the revision number after its created

Expected behavior:
It should start at revision 1.

Screenshots (if relevant):
I just created the top 3 configurations and they all start at rev 2.
image

@mostlyjason mostlyjason added bug Fixes for quality problems that affect the customer experience Team:Fleet Team label for Observability Data Collection Fleet team labels Jul 14, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/ingest-management (Team:Ingest Management)

@ph
Copy link
Contributor

ph commented Jul 15, 2020

This isn't great UI but I don't find it critical, I believe its because we do two saves on the Agent configuration document?

@nchaulet
Copy link
Member

Yes it because we create the configuration and add the datasource after that cause a bump of revision.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants