sourcegraph/internal/telemetry
Aditya Kalia 0777ced17f
V2-telemetry: Simplify sensitive metadata allowlist to accept feature only (#63325)
This PR adds another option to the sensitive metadata allowlist by
simplifying the input requirements. to accept `feature` and the
allowlisted `privateMetadata` keys for that feature.

This change is particularly beneficial when a `feature` has multiple
associated `action`(s), and the `privateMetadata` key needs to be
allowed for all events related to that feature.

Building upon this initial PR:
- https://github.com/sourcegraph/sourcegraph/pull/62830/files

<!-- 💡 To write a useful PR description, make sure that your description
covers:
- WHAT this PR is changing:
    - How was it PREVIOUSLY.
    - How it will be from NOW on.
- WHY this PR is needed.
- CONTEXT, i.e. to which initiative, project or RFC it belongs.

The structure of the description doesn't matter as much as covering
these points, so use
your best judgement based on your context.
Learn how to write good pull request description:
https://www.notion.so/sourcegraph/Write-a-good-pull-request-description-610a7fd3e613496eb76f450db5a49b6e?pvs=4
-->


## Test plan

<!-- All pull requests REQUIRE a test plan:
https://docs-legacy.sourcegraph.com/dev/background-information/testing_principles
-->
CI and unit tests

## Changelog

<!--
1. Ensure your pull request title is formatted as: $type($domain): $what
2. Add bullet list items for each additional detail you want to cover
(see example below)
3. You can edit this after the pull request was merged, as long as
release shipping it hasn't been promoted to the public.
4. For more information, please see this how-to
https://www.notion.so/sourcegraph/Writing-a-changelog-entry-dd997f411d524caabf0d8d38a24a878c?

Audience: TS/CSE > Customers > Teammates (in that order).

Cheat sheet: $type = chore|fix|feat $domain:
source|search|ci|release|plg|cody|local|...
-->

<!--
Example:

Title: fix(search): parse quotes with the appropriate context
Changelog section:

## Changelog

- When a quote is used with regexp pattern type, then ...
- Refactored underlying code.
-->
2024-06-27 15:22:58 -04:00
..
sensitivemetadataallowlist V2-telemetry: Simplify sensitive metadata allowlist to accept feature only (#63325) 2024-06-27 15:22:58 -04:00
telemetryrecorder internal/telemetry: make adding EventsStore middleware easier (#63216) 2024-06-13 11:55:06 +01:00
telemetrystore internal/telemetry: make adding EventsStore middleware easier (#63216) 2024-06-13 11:55:06 +01:00
telemetrytest bazel: transcribe test ownership to bazel tags (#62664) 2024-05-16 15:51:16 +01:00
besteffort.go telemetry-gateway: distinguish between retryable/nonretryable errors, telemetry: add callsite validation of feature/action (#61906) 2024-04-16 10:42:17 -07:00
billing_categories.go telemetry: init internal APIs and events cache store layer (#56520) 2023-09-19 21:53:42 -07:00
billing_products.go telemetry: init internal APIs and events cache store layer (#56520) 2023-09-19 21:53:42 -07:00
BUILD.bazel internal/telemetry: make adding EventsStore middleware easier (#63216) 2024-06-13 11:55:06 +01:00
CODENOTIFY chore: convert nested CODEOWNERS to CODENOTIFY (#61936) 2024-04-16 18:03:26 +00:00
events.go fix/telemetry(auth): return authenticated context from session.SetActorFromUser (#62701) 2024-05-15 16:48:42 -07:00
telemetry_test.go internal/telemetry: make adding EventsStore middleware easier (#63216) 2024-06-13 11:55:06 +01:00
telemetry.go telemetry/resolvers, internal/telemetry, telemetry-gateway: validate feature/action (#62214) 2024-04-29 19:34:50 +00:00
telemetrygateway_test.go telemetry: support float64 attributes (#58643) 2023-11-29 08:11:09 -08:00
telemetrygateway.go lib/telemetrygateway: publish all non-Sourcegraph-specific Telemetry Gateway bindings (#62061) 2024-04-22 14:36:46 -07:00