Support new CSP auth method for Wavefront (AOA) #4054
Labels
enhancement
A general enhancement
registry: wavefront
A Wavefront (Tanzu Observability) Registry related issue
spring-boot change
Change is needed in Spring Boot for this issue
Milestone
Please describe the feature request.
Wavefront has integrated into VMware's CSP authentication system, and the
wavefront-sdk-java
library has been updated to support that. We would like micrometer to support this additional authentication method inWavefrontMeterRegistry
Rationale
New Wavefront customers will be onboarded to CSP-only clusters, and the existing authentication method of WF API Token will not be available to them. To allow these customers to use micrometer for sending metrics to Wavefront, they'll need CSP authentication available.
Additional context
The release version of
wavefront-sdk-java
with these changes is3.4.0
.There are two types of CSP authentication: server-to-server tokens and user-api-tokens. We envision the changes looking something like this:
CSP User API Token
WavefrontMeterRegistry
, something likenew WavefrontClient.Builder(getWavefrontReportingUri(config), config.cspApiToken()).useTokenForCSP()
CSP Server to Server OAuth
WavefrontMeterRegistry
, something likenew WavefrontClient.Builder(getWavefrontReportingUri(config), config.cspClientId(), config.cspClientSecret())
builder.cspOrgId(config.cspOrgId())
Note that CSP Authentication is only valid for Direct Ingestion scenarios (like
DEFAULT_DIRECT
inWavefrontConfig
). It is not relevant for theDEFAULT_PROXY
case.Last, we've created a similar issue for Spring Boot: spring-projects/spring-boot#37165
Thank you!
– @oppegard and @warshawd
The text was updated successfully, but these errors were encountered: