Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support expose envoy metrics for plugins #820

Open
wonderflow opened this issue Dec 11, 2024 · 2 comments · May be fixed by #827
Open

Support expose envoy metrics for plugins #820

wonderflow opened this issue Dec 11, 2024 · 2 comments · May be fixed by #827
Labels

Comments

@wonderflow
Copy link
Contributor

wonderflow commented Dec 11, 2024

Description

Envoy has metrics for filters to get an overview of the plugin execution statistics, we need to expose metrics for plugins.

Use Scenes

Just like the envoy filters, e.g. the global rate-limiting has metric statistics to describe how many requests has over the limitation. It can also help us for troubleshooting.

Advice

thanks to @spacewander for the suggestions below:
Envoy Go metric API: https://github.com/envoyproxy/envoy/blob/0ff8fc30ae72a5a0efdc7d651f217021c77056b3/contrib/golang/common/go/api/filter.go#L312
While htnn not inetgrated yet, we need to enhance this part:

fc.InitFailure = initer.Init(nil)

@spacewander
Copy link
Member

More precisely, it is

func (p *FilterManagerConfigParser) Parse(any *anypb.Any, callbacks capi.ConfigCallbackHandler) (interface{}, error) {

@wonderflow wonderflow linked a pull request Dec 18, 2024 that will close this issue
Copy link

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged with no stale labels or other activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Jan 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants