hypertrace

hypertrace copied to clipboard

kotharironak

kotharironak

##Description Made 2 PR to improve underlying helm charts: - [config-bootstrapper](https://github.com/hypertrace/config-bootstrapper/pull/64) configuring initContainer from values.yaml allowing installation pulling image from over-writable repo - [pinot](https://github.com/hypertrace/pinot/pull/94) adding flag to enable/disable prometheusRule based...

tomassatka

As part of Phase1, the existing metrics - call count/error count/latency - mainly for service, backend, and API entities first, will be extracted at the end of the ingestion pipeline...

kotharironak

Exclude Spans from messaging system in endpoint traces

2

Screen: Service endpoints screen ( /services/service/\/endpoints) Endpoint traces should be showing when the spans are touching entry/exit boundaries of a service. Spans from messaging system do not fit here naturally....

asldevi

## Description Please include a summary of the change, motivation and context. ### Testing Please describe the tests that you ran to verify your changes. Please summarize what did you...

kamaleshnneerasa

kotharironak

Refer https://github.com/hypertrace/hypertrace-alert-engine/pull/80#discussion_r743763330

findingrish

[Feature Request] Alerting support for metric series

5

## Use Case Currently, HT supports following out-of-box time series metrics for service and API entities based on tracing data. - call rate - error rate - latency There are...

kotharironak

findingrish