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.

Sign up for GitHub

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

Jump to bottom

[Agent] Log that the Agent is an alpha release #17328

Closed
ph opened this issue Mar 30, 2020 · 1 comment · Fixed by #17336
Closed

[Agent] Log that the Agent is an alpha release #17328

ph opened this issue Mar 30, 2020 · 1 comment · Fixed by #17336
Assignees
@ph

Comments

@ph
Copy link
Contributor

ph commented Mar 30, 2020

We should add a clear statement about the stability of the agent in:

  • The log at startup.
  • When we run the enroll command.
@elasticmachine
Copy link
Collaborator

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

@ph ph self-assigned this Mar 30, 2020
ph added a commit to ph/beats that referenced this issue Mar 30, 2020
@ph
Display the stability status of the Elastic Agent
7b5bd04 
The Elastic Agent is currently Alpha quality software and is not ready
to be used in a production environment, this commit make it obvious in
the logs on startup and at enrollment.

Note this doesn't use the cfgwarn helpers for two reasons:

- We aren't using zap in the Elastic Agent code.
- We also need to print on standout.

This also add a "warn" package where the messaging can be edited once.

Fixes: elastic#17328
@ph ph mentioned this issue Mar 30, 2020
Merged
6 tasks
@ph ph closed this as completed in #17336 Mar 31, 2020
ph added a commit that referenced this issue Mar 31, 2020
@ph
Display the stability status of the Elastic Agent (#17336)
b70e44b 
* Display the stability status of the Elastic Agent

The Elastic Agent is currently Alpha quality software and is not ready
to be used in a production environment, this commit make it obvious in
the logs on startup and at enrollment.

Note this doesn't use the cfgwarn helpers for two reasons:

- We aren't using zap in the Elastic Agent code.
- We also need to print on standout.

This also add a "warn" package where the messaging can be edited once.

Fixes: #17328

* Add a changelog entry
ph added a commit to ph/beats that referenced this issue Apr 7, 2020
@ph
Display the stability status of the Elastic Agent (elastic#17336)
5a2429b 
* Display the stability status of the Elastic Agent

The Elastic Agent is currently Alpha quality software and is not ready
to be used in a production environment, this commit make it obvious in
the logs on startup and at enrollment.

Note this doesn't use the cfgwarn helpers for two reasons:

- We aren't using zap in the Elastic Agent code.
- We also need to print on standout.

This also add a "warn" package where the messaging can be edited once.

Fixes: elastic#17328

* Add a changelog entry

(cherry picked from commit b70e44b)
@ph ph mentioned this issue Apr 7, 2020
Merged
6 tasks
ph added a commit that referenced this issue Apr 7, 2020
@ph
Display the stability status of the Elastic Agent (#17336) (#17578)
9c844df 
* Display the stability status of the Elastic Agent

The Elastic Agent is currently Alpha quality software and is not ready
to be used in a production environment, this commit make it obvious in
the logs on startup and at enrollment.

Note this doesn't use the cfgwarn helpers for two reasons:

- We aren't using zap in the Elastic Agent code.
- We also need to print on standout.

This also add a "warn" package where the messaging can be edited once.

Fixes: #17328

* Add a changelog entry

(cherry picked from commit b70e44b)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ph ph

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Display the stability status of the Elastic Agent ph/beats
2 participants
@ph @elasticmachine