Skip to content

Commit 526d36c

Browse files
authored
Add mahadzaryab1 to maintainers (#6323)
## Which problem is this PR solving? - Resolves #6264 ## Description of the changes - Add new maintainer - Clean-up README --------- Signed-off-by: Yuri Shkuro <[email protected]>
1 parent 56c09d3 commit 526d36c

File tree

4 files changed

+33
-124
lines changed

4 files changed

+33
-124
lines changed

GOVERNANCE.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -57,13 +57,11 @@ Former maintainers can be reinstated to full maintainer status through the same
5757

5858
## Emeritus Maintainers
5959

60-
Former maintainers are recognized with an honorary _Emeritus Maintainer_ status, and have their names permanently
61-
listed in the README as a form of gratitude for their contributions.
60+
Former maintainers are recognized with an honorary _Emeritus Maintainer_ status, and have their names permanently listed in the [MAINTAINERS](./MAINTAINERS.md#emeritus-maintainers) file as a form of gratitude for their contributions.
6261

6362
## GitHub Project Administration
6463

65-
Maintainers will be added to the GitHub @jaegertracing/jaeger-maintainers team, and made a GitHub maintainer of that team.
66-
They will be given write permission to the Jaeger GitHub repository https://github.com/jaegertracing/jaeger.
64+
Maintainers will be added to the GitHub @jaegertracing/jaeger-maintainers team, and made a GitHub maintainer of that team. They will be given write permission to the Jaeger GitHub repository https://github.com/jaegertracing/jaeger.
6765

6866
## Changes in Governance
6967

MAINTAINERS.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,20 @@ The current Maintainers Group for the Jaeger Project consists of:
55
| [@albertteoh](https://github.com/albertteoh) | PackSmith | ALL |
66
| [@jkowall](https://github.com/jkowall) | Aiven | ALL |
77
| [@joe-elliott](https://github.com/joe-elliott) | Grafana Labs | ALL |
8+
| [@mahadzaryab1](https://github.com/mahadzaryab1) | Bloomberg | ALL |
89
| [@pavolloffay](https://github.com/pavolloffay) | RedHat | ALL |
910
| [@yurishkuro](https://github.com/yurishkuro) | Meta | ALL |
1011

1112
This list must be kept in sync with the [CNCF Project Maintainers list](https://github.com/cncf/foundation/blob/master/project-maintainers.csv).
1213

1314
See [the project Governance](./GOVERNANCE.md) for how maintainers are selected and replaced.
15+
16+
### Emeritus Maintainers
17+
18+
We are grateful to our former maintainers for their contributions to the Jaeger project.
19+
20+
* [@black-adder](https://github.com/black-adder)
21+
* [@jpkrohling](https://github.com/jpkrohling)
22+
* [@objectiser](https://github.com/objectiser)
23+
* [@tiffon](https://github.com/tiffon)
24+
* [@vprithvi](https://github.com/vprithvi)

README.md

Lines changed: 14 additions & 115 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@
1616

1717
# Jaeger - a Distributed Tracing System
1818

19-
💥💥💥 Jaeger v2 is coming! Read the [blog post](https://medium.com/jaegertracing/towards-jaeger-v2-moar-opentelemetry-2f8239bee48e) and [try it out](./cmd/jaeger).
19+
💥💥💥 Jaeger v2 is out! Read the [blog post](https://medium.com/jaegertracing/jaeger-v2-released-09a6033d1b10) and [try it out](https://www.jaegertracing.io/docs/latest/getting-started/).
2020

2121
```mermaid
2222
graph TD
@@ -35,93 +35,16 @@ graph TD
3535
end
3636
```
3737

38-
Jaeger, inspired by [Dapper][dapper] and [OpenZipkin](https://zipkin.io),
39-
is a distributed tracing platform created by [Uber Technologies][ubeross]
40-
and donated to [Cloud Native Computing Foundation](https://cncf.io).
41-
It can be used for monitoring microservices-based distributed systems:
38+
Jaeger is a distributed tracing platform created by [Uber Technologies](https://eng.uber.com/distributed-tracing/) and donated to [Cloud Native Computing Foundation](https://cncf.io).
4239

43-
* Distributed context propagation
44-
* Distributed transaction monitoring
45-
* Root cause analysis
46-
* Service dependency analysis
47-
* Performance / latency optimization
40+
See Jaeger [documentation][doc] for getting started, operational details, and other information.
4841

49-
See also:
50-
51-
* Jaeger [documentation][doc] for getting started, operational details, and other information.
52-
* Blog post [Evolving Distributed Tracing at Uber](https://eng.uber.com/distributed-tracing/).
53-
* Tutorial / walkthrough [Take Jaeger for a HotROD ride][hotrod-tutorial].
54-
55-
Jaeger is hosted by the [Cloud Native Computing Foundation](https://cncf.io) (CNCF) as the 7th top-level project (graduated in October 2019). If you are a company that wants to help shape the evolution of technologies that are container-packaged, dynamically-scheduled and microservices-oriented, consider joining the CNCF. For details about who's involved and how Jaeger plays a role, read the CNCF [Jaeger incubation announcement](https://www.cncf.io/blog/2017/09/13/cncf-hosts-jaeger/) and [Jaeger graduation announcement](https://www.cncf.io/announcement/2019/10/31/cloud-native-computing-foundation-announces-jaeger-graduation/).
42+
Jaeger is hosted by the [Cloud Native Computing Foundation](https://cncf.io) (CNCF) as the 7th top-level project, graduated in October 2019. See the CNCF [Jaeger incubation announcement](https://www.cncf.io/blog/2017/09/13/cncf-hosts-jaeger/) and [Jaeger graduation announcement](https://www.cncf.io/announcement/2019/10/31/cloud-native-computing-foundation-announces-jaeger-graduation/).
5643

5744
## Get Involved
5845

5946
Jaeger is an open source project with open governance. We welcome contributions from the community, and we would love your help to improve and extend the project. Here are [some ideas](https://www.jaegertracing.io/get-involved/) for how to get involved. Many of them do not even require any coding.
6047

61-
## Features
62-
63-
### High Scalability
64-
65-
Jaeger backend is designed to have no single points of failure and to scale with the business needs.
66-
For example, any given Jaeger installation at Uber is typically processing several billions of spans per day.
67-
68-
### Relationship with OpenTelemetry
69-
70-
The Jaeger and [OpenTelemetry](https://opentelemetry.io) projects have different goals. OpenTelemetry aims to provide APIs and SDKs in multiple languages to allow applications to export various telemetry data out of the process, to any number of metrics and tracing backends. The Jaeger project is primarily the tracing backend that receives tracing telemetry data and provides processing, aggregation, data mining, and visualizations of that data. For more information please refer to a blog post [Jaeger and OpenTelemetry](https://medium.com/jaegertracing/jaeger-and-opentelemetry-1846f701d9f2).
71-
72-
Jaeger was originally designed to support the [OpenTracing standard](https://opentracing.io/specification/). The terminology is still used in Jaeger UI, but the concepts have direct mapping to the OpenTelemetry data model of traces.
73-
74-
| Capability | OpenTracing concept | OpenTelemetry concept |
75-
| ------------- | ------------------- | --------------------- |
76-
| Represent traces as directed acyclic graphs (not just trees) | [span references](https://github.com/opentracing/specification/blob/master/specification.md#references-between-spans) | [span links](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#span) |
77-
| Strongly typed span attributes | span tags | span attributes |
78-
| Strongly typed events/logs | span logs | span events |
79-
80-
Jaeger project recommends OpenTelemetry SDKs for instrumentation, instead of [now-deprecated Jaeger SDKs](https://www.jaegertracing.io/docs/latest/client-libraries/#deprecating-jaeger-clients).
81-
82-
### Multiple storage backends
83-
84-
Jaeger can be used with a growing a number of storage backends:
85-
* It natively supports two popular open source NoSQL databases as trace storage backends: Cassandra and Elasticsearch.
86-
* It integrates via a gRPC API with other well known databases that have been certified to be Jaeger compliant: [TimescaleDB via Promscale](https://github.com/timescale/promscale), [ClickHouse](https://github.com/jaegertracing/jaeger-clickhouse).
87-
* There is embedded database support using [Badger](https://github.com/dgraph-io/badger) and simple in-memory storage for testing setups.
88-
* ScyllaDB [can be used](https://github.com/jaegertracing/jaeger/blob/main/plugin/storage/scylladb/README.md) as a drop-in replacement for Cassandra since it uses the same data model and query language.
89-
* There are ongoing community experiments using other databases, such as InfluxDB, Amazon DynamoDB, YugabyteDB(YCQL).
90-
91-
### Modern Web UI
92-
93-
Jaeger Web UI is implemented in Javascript using popular open source frameworks like React. Several performance
94-
improvements have been released in v1.0 to allow the UI to efficiently deal with large volumes of data and to display
95-
traces with tens of thousands of spans (e.g. we tried a trace with 80,000 spans).
96-
97-
### Cloud Native Deployment
98-
99-
Jaeger backend is distributed as a collection of Docker images. The binaries support various configuration methods,
100-
including command line options, environment variables, and configuration files in multiple formats (yaml, toml, etc.).
101-
102-
The recommended way to deploy Jaeger in a production Kubernetes cluster is via the [Jaeger Operator](https://github.com/jaegertracing/jaeger-operator).
103-
104-
The Jaeger Operator provides a [CLI to generate](https://github.com/jaegertracing/jaeger-operator#experimental-generate-kubernetes-manifest-file) Kubernetes manifests from the Jaeger CR.
105-
This can be considered as an alternative source over plain Kubernetes manifest files.
106-
107-
The Jaeger ecosystem also provides a [Helm chart](https://github.com/jaegertracing/helm-charts) as an alternative way to deploy Jaeger.
108-
109-
### Observability
110-
111-
All Jaeger backend components expose [Prometheus](https://prometheus.io/) metrics by default (other metrics backends are
112-
also supported). Logs are written to standard out using the structured logging library [zap](https://github.com/uber-go/zap).
113-
114-
### Security
115-
116-
Third-party security audits of Jaeger are available in https://github.com/jaegertracing/security-audits. Please see [Issue #1718](https://github.com/jaegertracing/jaeger/issues/1718) for the summary of available security mechanisms in Jaeger.
117-
118-
### Backwards compatibility with Zipkin
119-
120-
Although we recommend instrumenting applications with OpenTelemetry, if your organization has already invested in the instrumentation
121-
using Zipkin libraries, you do not have to rewrite all that code. Jaeger provides backwards compatibility with Zipkin
122-
by accepting spans in Zipkin formats (Thrift or JSON v1/v2) over HTTP. Switching from Zipkin backend is just a matter
123-
of routing the traffic from Zipkin libraries to the Jaeger backend.
124-
12548
## Version Compatibility Guarantees
12649

12750
Occasionally, CLI flags can be deprecated due to, for example, usability improvements or new functionality.
@@ -151,24 +74,16 @@ Starting with the release of Go 1.21, support for Go versions will be updated as
15174

15275
## Related Repositories
15376

154-
### Documentation
155-
156-
* Published: https://www.jaegertracing.io/docs/
157-
* Source: https://github.com/jaegertracing/documentation
158-
159-
### Instrumentation Libraries
160-
161-
Jaeger project recommends OpenTelemetry SDKs for instrumentation, instead of Jaeger's native SDKs [that are now deprecated](https://www.jaegertracing.io/docs/latest/client-libraries/#deprecating-jaeger-clients).
162-
163-
### Deployment
164-
165-
* [Jaeger Operator for Kubernetes](https://github.com/jaegertracing/jaeger-operator#getting-started)
166-
16777
### Components
16878

16979
* [UI](https://github.com/jaegertracing/jaeger-ui)
17080
* [Data model](https://github.com/jaegertracing/jaeger-idl)
17181

82+
### Documentation
83+
84+
* Published: https://www.jaegertracing.io/docs/
85+
* Source: https://github.com/jaegertracing/documentation
86+
17287
## Building From Source
17388

17489
See [CONTRIBUTING](./CONTRIBUTING.md).
@@ -186,27 +101,11 @@ Thanks to all the people who already contributed!
186101
### Maintainers
187102

188103
Rules for becoming a maintainer are defined in the [GOVERNANCE](./GOVERNANCE.md) document.
189-
Below are the official maintainers of the Jaeger project.
104+
The official maintainers of the Jaeger project are listed in the [MAINTAINERS](./MAINTAINERS.md) file.
190105
Please use `@jaegertracing/jaeger-maintainers` to tag them on issues / PRs.
191106

192-
* [@albertteoh](https://github.com/albertteoh)
193-
* [@jkowall](https://github.com/jkowall)
194-
* [@joe-elliott](https://github.com/joe-elliott)
195-
* [@pavolloffay](https://github.com/pavolloffay)
196-
* [@yurishkuro](https://github.com/yurishkuro)
197-
198107
Some repositories under [jaegertracing](https://github.com/jaegertracing) org have additional maintainers.
199108

200-
### Emeritus Maintainers
201-
202-
We are grateful to our former maintainers for their contributions to the Jaeger project.
203-
204-
* [@black-adder](https://github.com/black-adder)
205-
* [@jpkrohling](https://github.com/jpkrohling)
206-
* [@objectiser](https://github.com/objectiser)
207-
* [@tiffon](https://github.com/tiffon)
208-
* [@vprithvi](https://github.com/vprithvi)
209-
210109
## Project Status Meetings
211110

212111
The Jaeger maintainers and contributors meet regularly on a video call. Everyone is welcome to join, including end users. For meeting details, see https://www.jaegertracing.io/get-in-touch/.
@@ -223,6 +122,10 @@ Have questions, suggestions, bug reports? Reach the project community via these
223122
* [`jaeger-tracing` mail group](https://groups.google.com/forum/#!forum/jaeger-tracing)
224123
* GitHub [issues](https://github.com/jaegertracing/jaeger/issues) and [discussions](https://github.com/jaegertracing/jaeger/discussions)
225124

125+
## Security
126+
127+
Third-party security audits of Jaeger are available in https://github.com/jaegertracing/security-audits. Please see [Issue #1718](https://github.com/jaegertracing/jaeger/issues/1718) for the summary of available security mechanisms in Jaeger.
128+
226129
## Adopters
227130

228131
Jaeger as a product consists of multiple components. We want to support different types of users,
@@ -238,8 +141,6 @@ If you would like to add your organization to the list, please comment on our
238141
Copyright (c) The Jaeger Authors. [Apache 2.0 License](./LICENSE).
239142

240143
[doc]: https://jaegertracing.io/docs/
241-
[godoc-img]: https://godoc.org/github.com/jaegertracing/jaeger?status.svg
242-
[godoc]: https://godoc.org/github.com/jaegertracing/jaeger
243144
[ci-img]: https://github.com/jaegertracing/jaeger/actions/workflows/ci-unit-tests.yml/badge.svg?branch=main
244145
[ci]: https://github.com/jaegertracing/jaeger/actions/workflows/ci-unit-tests.yml?query=branch%3Amain
245146
[cov-img]: https://codecov.io/gh/jaegertracing/jaeger/branch/main/graph/badge.svg
@@ -256,8 +157,6 @@ Copyright (c) The Jaeger Authors. [Apache 2.0 License](./LICENSE).
256157
[artifacthub]: https://artifacthub.io/packages/search?repo=jaegertracing
257158

258159

259-
[dapper]: https://research.google.com/pubs/pub36356.html
260-
[ubeross]: https://uber.github.io
261160
[community-badge]: https://img.shields.io/badge/Project+Community-stats-blue.svg
262161
[community-stats]: https://all.devstats.cncf.io/d/54/project-health?orgId=1&var-repogroup_name=Jaeger
263162
[hotrod-tutorial]: https://medium.com/jaegertracing/take-jaeger-for-a-hotrod-ride-233cf43e46c2

RELEASE.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -78,8 +78,9 @@ Here are the release managers for future versions with the tentative release dat
7878
7979
| Version | Release Manager | Tentative release date |
8080
|---------|-----------------|------------------------|
81-
| 1.65.0 | @jkowall | 8 January 2025 |
82-
| 1.66.0 | @yurishkuro | 3 February 2025 |
83-
| 1.67.0 | @albertteoh | 5 March 2025 |
84-
| 1.68.0 | @pavolloffay | 5 April 2025 |
85-
| 1.69.0 | @joe-elliott | 7 May 2025 |
81+
| 1.65.0 | @mahadzaryab1 | 8 January 2025 |
82+
| 1.66.0 | @jkowall | 3 February 2025 |
83+
| 1.67.0 | @yurishkuro | 5 March 2025 |
84+
| 1.68.0 | @albertteoh | 5 April 2025 |
85+
| 1.69.0 | @pavolloffay | 7 May 2025 |
86+
| 1.70.0 | @joe-elliott | 5 June 2025 |

0 commit comments

Comments
 (0)