-
Notifications
You must be signed in to change notification settings - Fork 143
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
[helm]: implement system integration as chart built-in #5855
Changes from all commits
3dd64de
b0239d6
70205a8
da31f5e
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
# Example: System Integration with custom auth log paths | ||
|
||
In this example we install the built-in `system` integration and specify custom paths for the auth logs stream (see [agent-system-values.yaml](agent-system-values.yaml)). | ||
|
||
## Prerequisites: | ||
1. A k8s secret that contains the connection details to an Elasticsearch cluster such as the URL and the API key ([Kibana - Creating API Keys](https://www.elastic.co/guide/en/kibana/current/api-keys.html)): | ||
```console | ||
kubectl create secret generic es-api-secret \ | ||
--from-literal=api_key=... \ | ||
--from-literal=url=... | ||
``` | ||
|
||
2. `system` integration assets installed through Kibana ([Kibana - Install and uninstall Elastic Agent integration assets](https://www.elastic.co/guide/en/fleet/current/install-uninstall-integration-assets.html)) | ||
|
||
## Run: | ||
```console | ||
helm install elastic-agent ../../ \ | ||
-f ./agent-system-values.yaml \ | ||
--set outputs.default.type=ESSecretAuthAPI \ | ||
--set outputs.default.secretName=es-api-secret | ||
``` | ||
|
||
## Validate: | ||
|
||
1. The Kibana `system`-related dashboards should start showing up the respective info. |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
system: | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We should have rendered examples for this, right? I thought the mage target would error in this case. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. hmm, I thought I added it but this never happened, but the CI should fail yes There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. oh I suspect that this is because the file was never versioned and the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Shouldn't it fail anyway if it can't find the file? I didn't know the examples mage target was aware of versioning. Anyway, this isn't a blocker for this PR, but we should make sure the check actually catches issues. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. the current CI checks flow is the following:
100% agreed this needs to be extended |
||
enabled: true | ||
authLogs: | ||
vars: | ||
paths: | ||
- /var/log/custom_auth.log | ||
syslog: | ||
vars: | ||
paths: | ||
- /var/log/custom_syslog.log | ||
|
||
agent: | ||
unprivileged: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is the default
false
? I feel like most will want this on, it brings immediate value to the Observability section in Kibana.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
More than happy to have it by default as
true
, it also makes sense to me. @nimarezainia what do you think on that? 🙂