This is an automated email from the ASF dual-hosted git repository.
bzp2010 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/apisix-website.git
The following commit(s) were added to refs/heads/master by this push:
new 009b906 docs: add weekly report 11.14 (#746)
009b906 is described below
commit 009b906aa5f01ef109088eb6e261428bd7be42eb
Author: lijing-21 <[email protected]>
AuthorDate: Mon Nov 15 14:59:24 2021 +0800
docs: add weekly report 11.14 (#746)
Co-authored-by: yilinzeng <[email protected]>
---
website/blog/2021/11/16/weekly-report-1114.md | 91 ++++++++++++++++++++++
.../2021/11/16/weekly-report-1114.md | 88 +++++++++++++++++++++
2 files changed, 179 insertions(+)
diff --git a/website/blog/2021/11/16/weekly-report-1114.md
b/website/blog/2021/11/16/weekly-report-1114.md
new file mode 100644
index 0000000..85116a8
--- /dev/null
+++ b/website/blog/2021/11/16/weekly-report-1114.md
@@ -0,0 +1,91 @@
+---
+title: Weekly Report｜11.1-11.4 Feature Highlights Update in Progress
+keywords:
+- Apache APISIX
+- Weekly Report
+- Contributor
+- APISIX
+- API Gateway
+- Apache
+description: The Apache APISIX Community Weekly Report hopes to help community
members better understand the weekly progress of the Apache APISIX community
and and facilitate everyone to participate in the Apache APISIX community.
+tags: [Events]
+---
+
+> From 11.1 to 11.14, 28 contributors submitted 114 commits for Apache APISIX.
Thank you all for your contributions to Apache APISIX. It is your selfless
contribution to make the Apache APISIX project better!
+
+<!--truncate-->
+
+## Introduction
+
+Apache APISIX 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 APISIX Community Weekly Report hopes to help community members better
understand the weekly progress of the Apache APISIX community and and
facilitate everyone to participate in the Apache APISIX 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/apisix/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/apisix/issues/5417
+
+**Issue description**:
+
+Currently, Apache APISIX will generate an id while initializing if the user
doesn't specify one, and it relies on the
[lua-resty-jit-uuid](https://github.com/thibaultcha/lua-resty-jit-uuid) library
but without an explicit seed.
+
+```Lua
+uuid.seed()
+ apisix_uid = uuid.generate_v4()
+ log.notice("not found apisix uid, generate a new one: ", apisix_uid)
+```
+
+While the jit-uuid library creates the seed by the process id and the time in
ngx_lua context.
+
+```Lua
+ 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
APISIX 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 apisix id might be duplicated,
and if the id is critical, this may cause some fatal problems in the business
scenarios.
+
+## Highlights of Recent Features
+
+- [APISIX support for installation on Arch
Linux](https://github.com/apache/apisix/pull/5350)（Contributor:
[rapiz1](https://github.com/rapiz1)）
+
+- [The APISIX limit-conn plugin supports multiple variables as
key](https://github.com/apache/apisix/pull/5354)（Contributor:
[Xunzhuo](https://github.com/Xunzhuo)）
+
+- [The APISIX limit-count plugin supports multiple variables as
key](https://github.com/apache/apisix/pull/5378)（Contributor:
[Xunzhuo](https://github.com/Xunzhuo)）
+
+- [APISIX Support for POST form as matching conditions in advanced
matching](https://github.com/apache/apisix/pull/5409)（Contributor:
[bzp2010](https://github.com/bzp2010)）
+
+- [APISIX adds datadog plugin for metrics
collection](https://github.com/apache/apisix/pull/5372)（Contributor:
[bisakhmondal](https://github.com/bisakhmondal)）
+
+- [APISIX adds skywalking logger plugin to push access Log data to SkyWalking
OAP server](https://github.com/apache/apisix/pull/5478)（Contributor:
[dmsolr](https://github.com/dmsolr)）
+
+The Apache APISIX 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 APISIX protects Airwallex data sovereignty through the gateway
layer](https://apisix.apache.org/blog/2021/11/03/airwallex-usercase)：
+
+ This article will bring you about how Airwallex uses Apache APISIX for
gateway layer deployment to strengthen the construction of data sovereignty.
+
+- [The observability of Apache
APISIX](https://apisix.apache.org/blog/2021/11/04/skywalking)：
+
+ This article introduces the observability capabilities of Apache APISIX and
how to improve the observability capabilities of Apache APISIX through Apache
SkyWalking.
+
+- [Cloud Monitoring with Datadog in Apache
APISIX](https://apisix.apache.org/blog/2021/11/12/apisix-datadog)：
+
+ Apache APISIX recently released a new plugin:
[APISIX-Datadog](https://apisix.apache.org/docs/apisix/next/plugins/datadog/),
to provide a deeper integration with Datadog. This article introduces the
APISIX-Datadog Plugin and its capabilities.
diff --git
a/website/i18n/zh/docusaurus-plugin-content-blog/2021/11/16/weekly-report-1114.md
b/website/i18n/zh/docusaurus-plugin-content-blog/2021/11/16/weekly-report-1114.md
new file mode 100644
index 0000000..4952104
--- /dev/null
+++
b/website/i18n/zh/docusaurus-plugin-content-blog/2021/11/16/weekly-report-1114.md
@@ -0,0 +1,88 @@
+---
+title: "社区周报｜11.1-11.14 功能亮点更新进行中"
+keywords:
+- Apache APISIX
+- 社区周报
+- APISIX
+- API Gateway
+- 贡献者
+description: “独行者速，众行者远”。Apache APISIX 社区周报希望可以帮助社区小伙伴们更好地掌握 Apache APISIX
社区的每周进展，方便大家参与到 Apache APISIX 社区中来。
+tags: [Events]
+---
+
+> 从 11.1 到 11.14, 有 28 位开发者为 Apache APISIX 提交了 114 个 commits。感谢这些小伙伴为 Apache
APISIX 添砖加瓦，是你们的无私付出，让 Apache APISIX 项目变得更好！
+
+<!--truncate-->
+
+## 导语
+
+Apache APISIX 从开源第一天就以社区方式成长，迅速成为全世界最活跃的开源 API 网关项目。这些成就，离不开社区小伙伴们的共同奋斗。
+
+“独行者速，众行者远”。Apache APISIX 社区周报希望可以帮助社区小伙伴们更好地掌握 Apache APISIX 社区的每周进展，方便大家参与到
Apache APISIX 社区中来。
+
+我们还整理了一些适合新来社区的小伙伴们参加的 issue！感兴趣的同学们，走过路过不要错过！
+
+## 贡献者统计
+
+
+
+
+
+## Good first issue
+
+### Issue #5400
+
+**链接**: https://github.com/apache/apisix/issues/5400
+
+**问题描述**：七层的 HTTP 日志是存储在 acccess.log 中的，那么四层代理 stream route
如何启用日志并自定义日志路径呢？传统的 OpenResty 是可以实现的。
+
+### Issue #5417
+
+**链接**: https://github.com/apache/apisix/issues/5417
+
+**问题描述**：目前，如果用户没有指定一个 ID，Apache APISIX 会在初始化时生成一个 ID，它依赖于
[lua-resty-jit-uuid](https://github.com/thibaultcha/lua-resty-jit-uuid)
库，但没有一个明确的
seed。[如下](https://github.com/apache/apisix/blob/4dafab5afa3293b3d72007517246e01da385f8ef/apisix/core/id.lua#L76-L78)：
+
+```Lua
+uuid.seed()
+ apisix_uid = uuid.generate_v4()
+ log.notice("not found apisix uid, generate a new one: ", apisix_uid)
+```
+
+而 jit-uuid 库通过 ngx_lua 环境中的进程 ID 和时间创建
seed，[如下](https://github.com/thibaultcha/lua-resty-jit-uuid/blob/82538049040ae85ff880b79886f21d8593140c7d/lib/resty/jit-uuid.lua#L53-L54):
+
+```Lua
+ if ngx then
+ seed = ngx.time() + ngx.worker.pid()
+```
+
+然而，在容器化环境中，进程 ID（主进程）可能是相同的，即 1 号进程，另外，如果用户试图通过部署资源在 Kubernetes 上部署 Apache
APISIX 集群，几个 Pod 的时间可能是相同的，因为 ngx.time 没有足够的精确性（只有毫秒级别）。所以生成的 APISIX ID
可能是重复的，如果这个 ID 是关键的，这可能会在业务场景中造成严重的后果。
+
+## 近期功能特性亮点
+
+- [APISIX 支持在 Arch Linux
上安装](https://github.com/apache/apisix/pull/5350)（贡献者：[rapiz1](https://github.com/rapiz1)）
+
+- [APISIX limit-conn 插件支持变量作为限流
key](https://github.com/apache/apisix/pull/5354)（贡献者：[Xunzhuo](https://github.com/Xunzhuo)）
+
+- [APISIX limit-count 插件支持变量作为限流
key](https://github.com/apache/apisix/pull/5378)（贡献者：[Xunzhuo](https://github.com/Xunzhuo)）
+
+- [APISIX 支持通过 POST
表单属性进行高级路由匹配](https://github.com/apache/apisix/pull/5409)（贡献者：[bzp2010](https://github.com/bzp2010)）
+
+- [APISIX 新增用于指标收集的 datadog
插件](https://github.com/apache/apisix/pull/5372)（贡献者：[bisakhmondal](https://github.com/bisakhmondal)）
+
+- [APISIX 新增 skywalking-logger 插件，可将 Access Log 数据推送到 SkyWalking OAP
服务器](https://github.com/apache/apisix/pull/5478)（贡献者：[dmsolr](https://github.com/dmsolr)）
+
+Apache APISIX 的项目官网和 Github 上的 issue 上已经积累了比较丰富的文档教程和使用经验，如果您遇到问题可以翻阅文档，用关键词在
issue 中搜索，也可以参与 issue 上的讨论，提出自己的想法和实践经验。
+
+## 近期博文推荐
+
+- [Apache APISIX 如何通过网关层为 Airwallex
数据主权保驾护航](https://apisix.apache.org/zh/blog/2021/11/03/airwallex-usercase)：
+
+ 本文将为大家带来关于 Airwallex 空中云汇是如何使用 Apache APISIX 进行网关层部署来加固数据主权方面的建设。
+
+- [浅谈 Apache APISIX
的可观测性](https://apisix.apache.org/zh/blog/2021/11/04/skywalking)：
+
+ 本文介绍了 Apache APISIX 的可观测性能力以及如何通过 Apache SkyWalking 提升Apache APISIX 的可观测性能力。
+
+- [APISIX-Datadog
插件发布，助力用户提高系统的可观测性](https://apisix.apache.org/zh/blog/2021/11/12/apisix-datadog)：
+
+ Apache APISIX
最近发布了一个新的插件：[APISIX-Datadog](https://apisix.apache.org/docs/apisix/next/plugins/datadog/)，以提供与
Datadog 监控平台的集成。这篇文章介绍了 APISIX-Datadog 插件的实现原理及功能。
