consul/agent/hcp
Ashvitha 1fcd7747d2
Backport of [HCP Telemetry] Periodic Refresh for Dynamic Telemetry Configuration into release/1.15.x (#18360)
[HCP Telemetry] Periodic Refresh for Dynamic Telemetry Configuration (#18168)

* OTElExporter now uses an EndpointProvider to discover the endpoint

* OTELSink uses a ConfigProvider to obtain filters and labels configuration

* improve tests for otel_sink

* Regex logic is moved into client for a method on the TelemetryConfig object

* Create a telemetry_config_provider and update deps to use it

* Fix conversion

* fix import newline

* Add logger to hcp client and move telemetry_config out of the client.go file

* Add a telemetry_config.go to refactor client.go

* Update deps

* update hcp deps test

* Modify telemetry_config_providers

* Check for nil filters

* PR review updates

* Fix comments and move around pieces

* Fix comments

* Remove context from client struct

* Moved ctx out of sink struct and fixed filters, added a test

* Remove named imports, use errors.New if not fformatting

* Remove HCP dependencies in telemetry package

* Add success metric and move lock only to grab the t.cfgHahs

* Update hash

* fix nits

* Create an equals method and add tests

* Improve telemetry_config_provider.go tests

* Add race test

* Add missing godoc

* Remove mock for MetricsClient

* Avoid goroutine test panics

* trying to kick CI lint issues by upgrading mod

* imprve test code and add hasher for testing

* Use structure logging for filters, fix error constants, and default to allow all regex

* removed hashin and modify logic to simplify

* Improve race test and fix PR feedback by removing hash equals and avoid testing the timer.Ticker logic, and instead unit test

* Ran make go-mod-tidy

* Use errtypes in the test

* Add changelog

* add safety check for exporter endpoint

* remove require.Contains by using error types, fix structure logging, and fix success metric typo in exporter

* Fixed race test to have changing config values

* Send success metric before modifying config

* Avoid the defer and move the success metric under
2023-08-02 13:38:00 -04:00
..
bootstrap Backport of [CC-5718] Remove HCP token requirement during bootstrap (#18288) 2023-07-27 09:28:25 -07:00
client Backport of [HCP Telemetry] Periodic Refresh for Dynamic Telemetry Configuration into release/1.15.x (#18360) 2023-08-02 13:38:00 -04:00
config HCP Add node id/name to config (#17750) (#17795) 2023-06-16 19:23:39 +00:00
discover HCP Telemetry Feature (#17460) (#17502) 2023-05-29 17:02:52 -04:00
scada Update HCP bootstrapping to support existing clusters 1.15.x version (#17305) 2023-05-12 23:01:18 +02:00
telemetry Backport of [HCP Telemetry] Periodic Refresh for Dynamic Telemetry Configuration into release/1.15.x (#18360) 2023-08-02 13:38:00 -04:00
testserver add HCP integration component (#14723) 2022-09-26 14:58:15 -04:00
deps.go Backport of [HCP Telemetry] Periodic Refresh for Dynamic Telemetry Configuration into release/1.15.x (#18360) 2023-08-02 13:38:00 -04:00
deps_test.go Backport of [HCP Telemetry] Periodic Refresh for Dynamic Telemetry Configuration into release/1.15.x (#18360) 2023-08-02 13:38:00 -04:00
manager.go HCP Telemetry Feature (#17460) (#17502) 2023-05-29 17:02:52 -04:00
manager_test.go Backport of [HCP Telemetry] Periodic Refresh for Dynamic Telemetry Configuration into release/1.15.x (#18360) 2023-08-02 13:38:00 -04:00
telemetry_provider.go Backport of [HCP Telemetry] Periodic Refresh for Dynamic Telemetry Configuration into release/1.15.x (#18360) 2023-08-02 13:38:00 -04:00
telemetry_provider_test.go Backport of [HCP Telemetry] Periodic Refresh for Dynamic Telemetry Configuration into release/1.15.x (#18360) 2023-08-02 13:38:00 -04:00
testing.go Update HCP bootstrapping to support existing clusters 1.15.x version (#17305) 2023-05-12 23:01:18 +02:00