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

[Release] logzio-monitoring 6.2.2 #563

Merged
merged 4 commits into from
Nov 20, 2024
Merged

[Release] logzio-monitoring 6.2.2 #563

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
4975ca6
Upgrade `logzio-telemetry` chart to `v4.3.0`
yotamloe Nov 20, 2024
e94d58d
fix indent
yotamloe Nov 20, 2024
747f490
fix typo
yotamloe Nov 20, 2024
451140a
change test namespace -> `default`
yotamloe Nov 20, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions charts/logzio-monitoring/Chart.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ apiVersion: v2
name: logzio-monitoring
description: logzio-monitoring allows you to ship logs, metrics, traces and security reports from your Kubernetes cluster using the OpenTelemetry collector for metrics and traces, Fluentd for logs, and Trivy for security reports.
type: application
version: 6.2.1
version: 6.2.2



Expand All @@ -14,7 +14,7 @@ dependencies:
repository: "https://logzio.github.io/logzio-helm/"
condition: logs.enabled
- name: logzio-k8s-telemetry
version: "4.2.9"
version: "4.3.0"
repository: "https://logzio.github.io/logzio-helm/"
condition: metricsOrTraces.enabled
- name: logzio-trivy
Expand Down
4 changes: 3 additions & 1 deletion charts/logzio-monitoring/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -226,8 +226,10 @@ There are two possible approaches to the upgrade you can choose from:
- Reinstall the chart.
- Before running the `helm upgrade` command, delete the old subcharts resources: `logzio-monitoring-prometheus-pushgateway` deployment and the `logzio-monitoring-prometheus-node-exporter` daemonset.


## Changelog
- **6.2.2**:
- Upgrade `logzio-telemetry` chart to `v4.3.0`
- Set `servicegraph` connector, `metrics_flush_interval` setting to `60s` to reduce outgoing connections
yotamloe marked this conversation as resolved.
Show resolved Hide resolved
- **6.2.1**:
- Upgrade `logzio-telemetry` chart to `v4.2.9`
- Add batch processor to the SPM pipeline, to reduce stress and increase efficiency.
Expand Down
Loading