From 11.1 to 11.14, 28 contributors submitted 114 commits for Apache . Thank you all for your contributions to Apache . It is your selfless contribution to make the Apache project better!

Introduction​

Apache has grown as a community from the first day of open source and has quickly become the most active open source API gateway project in the world. These achievements cannot be achieved without the joint efforts of our community partners.

"If you want to go fast, go alone.If you want to go far, go together." The Apache Community Weekly Report hopes to help community members better understand the weekly progress of the Apache community and and facilitate everyone to participate in the Apache community.

We have also compiled some issues suitable for newcomers to the community to participate in! If you are interested, don't miss it!

Contributor Statistics​

Good first issue​

Issue #5400​

Link: https://github.com/apache//issues/5400

Issue description: The HTTP logs for Layer 7 are stored in acccess.log, so how does the Layer 4 proxy stream route enable logging and customize the log path? Traditionally, OpenResty can be implemented.

Issue #5417​

Link: https://github.com/apache//issues/5417

Issue description:

Currently, Apache will generate an id while initializing if the user doesn't specify one, and it relies on the lua-resty-jit-uuid library but without an explicit seed.

uuid.seed() _uid = uuid.generate_v4() log.notice("not found  uid, generate a new one: ", _uid)

While the jit-uuid library creates the seed by the process id and the time in ngx_lua context.

        if ngx then            seed = ngx.time() + ngx.worker.pid()

However, in a containerized environment, the process id (the master process) might be the same, i.e. the No. 1 process, also, if users try to deploy Apache clusters on Kubernetes through the Deployment resource, the time might be the same for several Pods, since ngx.time doesn't have enough precisions (only at milliseconds level). so the generated id might be duplicated, and if the id is critical, this may cause some fatal problems in the business scenarios.

Highlights of Recent Features​

• support for installation on Arch Linux（Contributor: rapiz1）

• The limit-conn plugin supports multiple variables as key（Contributor: Xunzhuo）

• The limit-count plugin supports multiple variables as key（Contributor: Xunzhuo）

• Support for POST form as matching conditions in advanced matching（Contributor: bzp2010）

• adds datadog plugin for metrics collection（Contributor: bisakhmondal）

• adds skywalking logger plugin to push access Log data to SkyWalking OAP server（Contributor: dmsolr）

The Apache project website and the Github issue have accumulated a wealth of documentation and experience, so if you encounter problems, you can read the documentation, search the issue with keywords, or participate in the discussion on the issue to put forward your own ideas and practical experience.

Recent Blog Recommendations​

• How Apache protects Airwallex data sovereignty through the gateway layer：

  This article will bring you about how Airwallex uses Apache for gateway layer deployment to strengthen the construction of data sovereignty.

• The observability of Apache ：

  This article introduces the observability capabilities of Apache and how to improve the observability capabilities of Apache through Apache SkyWalking.

• Cloud Monitoring with Datadog in Apache ：

  Apache recently released a new plugin: -Datadog, to provide a deeper integration with Datadog. This article introduces the -Datadog Plugin and its capabilities.