Pavel
Pavel
Add Beholder sdk. Copy from https://github.com/smartcontractkit/chainlink-common/pull/681
Be able to send custom messages, traces, metrics from core main via Beholder Run ``` cd ~/repos/chainlink ./beholderdemo/start.sh ``` Tail kafka topic with custom messages emitted from chainlilnk ``` cd...
Add support for OTEL client base of OTLP/HTTP exporters
Implement Prometheus to OTel metrics conversion and export. Forwarder: - Gets metrics from prometheus.Gatherer and exports them to provided OTLP/GRPC endpoint. Uses piped Receiver and Exporter. Receiver: - Wraps [prometheusreceiver](github.com/open-telemetry/opentelemetry-collector-contrib/receiver/prometheusreceiver)...
Beholder heartbeat
Add support for TLS with HTTP/2 for beholder/chip-ingress client Related PR: https://github.com/smartcontractkit/chainlink-common/pull/1261 Jira: https://smartcontract-it.atlassian.net/browse/INFOPLAT-2234
## What - Add chipIngressClient field to telemetry Manager struct - Pass chipingress.Client to NewManager constructor - Add ChipIngressEnabled option to TelemetryIngress config Related PR's - https://github.com/smartcontractkit/chainlink-common/pull/1647 - https://github.com/smartcontractkit/chainlink-common/pull/1646 ##...
Scaffold ChIP ingress integration - Added stub ChipIngressBatchClient + tests to begin migration off wsrpc toward chipingress. - Integrated ChIP ingress agents (single & multitype) into telemetry manager behind config...
## Context Currently legacy telemetry is sent via OTI ingress (see https://github.com/smartcontractkit/chainlink/tree/develop/core/services/telemetry). Extend existing legacy telemetry sending mechanism to be able to use ChIP ingress instead of OTI Jira: https://smartcontract-it.atlassian.net/browse/INFOPLAT-2732...