You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[receiver/gitproviderreceiver] rename to githubreceiver (#34731)
**Description:** <Describe what has changed.>
Renames `gitproviderreceiver` to `githubreceiver` to better align with
OpenTelemetry Semantic Conventions v1.27.0+ and allow for tracing and
log signals in the future.
---------
Co-authored-by: Andrzej Stencel <[email protected]>
Co-authored-by: Pablo Baeyens <[email protected]>
The Git Provider receiver scrapes data from Version Control Systems (VCS) that use Git as their underlying technology.
14
+
The GitHub receiver receives data from [GitHub](https://github.com). As a
15
+
starting point it scrapes metrics from repositories but will be extended to
16
+
include traces and logs.
15
17
16
-
As a starting point, this receiver can infer many of the same core VCS metrics across vendors, while being able to receive additional data specific to vendors.
18
+
The current default set of metrics can be found in
19
+
[documentation.md](./documentation.md).
17
20
18
-
The current default set of metrics common across all vendors can be found in [documentation.md](./documentation.md).
19
-
20
-
These VCS metrics can be used as leading indicators ([capabilities][doracap]) to the [DORA][dorafour] metrics; helping provide insight into modern-day engineering practices.
21
+
These metrics can be used as leading indicators ([capabilities][doracap])
22
+
to the [DORA][dorafour] metrics; helping provide insight into modern-day
0 commit comments