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

[Release] logzio-telemetry Add batch processor to SPM and Metrics #556

Merged
merged 2 commits into from
Nov 17, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion charts/logzio-telemetry/Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ dependencies:
# to the chart and its templates, including the app version.
# Versions are expected to follow Semantic Versioning (https://semver.org/)

version: 4.2.8
version: 4.2.9


# This is the version number of the application being deployed. This version number should be
Expand Down
2 changes: 2 additions & 0 deletions charts/logzio-telemetry/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -412,6 +412,8 @@ If you don't want the sub charts to installed add the relevant flag per sub char


## Change log
* 4.2.9
- Add batch processor to the SPM pipeline, to reduce stress and increase efficiency.
* 4.2.8
- Upgrade `otel/opentelemetry-collector-contrib` image to `v0.108.0`
- Remove default resources `limits`
Expand Down
11 changes: 9 additions & 2 deletions charts/logzio-telemetry/values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -308,7 +308,7 @@ spmForwarderConfig:
pipelines:
traces/spm:
receivers: [jaeger, zipkin, otlp]
processors: [resourcedetection/all, attributes/env_id, k8sattributes]
processors: [resourcedetection/all, attributes/env_id, k8sattributes, batch]
exporters: [logging, otlp]
# Metrics standalone collector configuration
metricsConfig:
Expand All @@ -319,6 +319,7 @@ metricsConfig:
metrics:
datapoint:
- 'IsMatch(metric.name, "(${K8S_360_METRICS})") == true and attributes["logzio_app"] != "kubernetes360"'
batch: {}
exporters:
prometheusremotewrite/applications:
timeout: 30s
Expand Down Expand Up @@ -495,6 +496,7 @@ metricsConfig:
processors:
- attributes/env_id
- filter/kubernetes360
- batch
receivers:
- prometheus/infrastructure
- prometheus/cadvisor
Expand Down Expand Up @@ -673,6 +675,7 @@ k8sObjectsConfig:
- context: log
statements:
- delete_key(body["object"]["metadata"], "managedFields")
batch: {}
exporters:
logzio/object_logs:
account_token: "${OBJECTS_LOGS_TOKEN}"
Expand All @@ -683,7 +686,7 @@ k8sObjectsConfig:
pipelines:
logs/k8sobjects:
receivers: [k8sobjects/pull,k8sobjects/watch]
processors: [transform/pulled_object,transform/remove_managedfields,transform/log_type, resource/env_id]
processors: [transform/pulled_object,transform/remove_managedfields,transform/log_type, resource/env_id, batch]
exporters: [logzio/object_logs]
# Service graph metrics configuration
serviceGraph:
Expand Down Expand Up @@ -732,6 +735,7 @@ spanMetricsAgregator:
- action: update_label
label: span.name
new_label: operation
batch: {}
connectors:
spanmetrics:
aggregation_temporality: AGGREGATION_TEMPORALITY_CUMULATIVE
Expand Down Expand Up @@ -812,6 +816,7 @@ spanMetricsAgregator:
processors:
- metricstransform/metrics-rename
- metricstransform/labels-rename
- batch
receivers:
- spanmetrics
traces:
Expand Down Expand Up @@ -997,6 +1002,7 @@ daemonsetConfig:
actions:
- key: job_dummy
action: delete
batch: {}
exporters:
prometheusremotewrite/applications:
timeout: 30s
Expand Down Expand Up @@ -1188,6 +1194,7 @@ daemonsetConfig:
- filter/kubernetes360
# workaround for duplicate metrics sent from kubernetes-service-endpoints job
- attributes/remove_job_dummy
- batch
receivers:
- prometheus/infrastructure
- prometheus/cadvisor
Expand Down
Loading