-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Added support for GAUGE_LIST metric type #17721
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
Conversation
Prior to the changes, log emits a warning about an unknown gauge metric type when running pipeline-to-pipeline due to serialization of `{send_to:[pipeline_name]}`. This commit added support of List type to eliminate the warning.
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
This pull request does not have a backport label. Could you fix it @kaisecheng? 🙏
|
|
💚 Build Succeeded
History
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@Mergifyio backport 8.17 8.18 8.19 9.0 |
✅ Backports have been created
|
* Added support for GAUGE_LIST metric type Prior to the changes, log emits a warning about an unknown gauge metric type when running pipeline-to-pipeline due to serialization of `{send_to:[pipeline_name]}`. This commit added support of List type to eliminate the warning. (cherry picked from commit 909d66c)
* Added support for GAUGE_LIST metric type Prior to the changes, log emits a warning about an unknown gauge metric type when running pipeline-to-pipeline due to serialization of `{send_to:[pipeline_name]}`. This commit added support of List type to eliminate the warning. (cherry picked from commit 909d66c)
* Added support for GAUGE_LIST metric type Prior to the changes, log emits a warning about an unknown gauge metric type when running pipeline-to-pipeline due to serialization of `{send_to:[pipeline_name]}`. This commit added support of List type to eliminate the warning. (cherry picked from commit 909d66c)
* Added support for GAUGE_LIST metric type Prior to the changes, log emits a warning about an unknown gauge metric type when running pipeline-to-pipeline due to serialization of `{send_to:[pipeline_name]}`. This commit added support of List type to eliminate the warning. (cherry picked from commit 909d66c)
* Added support for GAUGE_LIST metric type Prior to the changes, log emits a warning about an unknown gauge metric type when running pipeline-to-pipeline due to serialization of `{send_to:[pipeline_name]}`. This commit added support of List type to eliminate the warning. (cherry picked from commit 909d66c) Co-authored-by: kaisecheng <[email protected]>
* Added support for GAUGE_LIST metric type Prior to the changes, log emits a warning about an unknown gauge metric type when running pipeline-to-pipeline due to serialization of `{send_to:[pipeline_name]}`. This commit added support of List type to eliminate the warning. (cherry picked from commit 909d66c) Co-authored-by: kaisecheng <[email protected]>
* Added support for GAUGE_LIST metric type Prior to the changes, log emits a warning about an unknown gauge metric type when running pipeline-to-pipeline due to serialization of `{send_to:[pipeline_name]}`. This commit added support of List type to eliminate the warning. (cherry picked from commit 909d66c) Co-authored-by: kaisecheng <[email protected]>
* Added support for GAUGE_LIST metric type Prior to the changes, log emits a warning about an unknown gauge metric type when running pipeline-to-pipeline due to serialization of `{send_to:[pipeline_name]}`. This commit added support of List type to eliminate the warning. (cherry picked from commit 909d66c) Co-authored-by: kaisecheng <[email protected]>
Release notes
Fixed warning in logs about an unknown type of metric.
What does this PR do?
added support of List type to eliminate the warning.
Why is it important/What is the impact to the user?
Prior to the changes, log emits a warning about an unknown gauge metric type when running pipeline-to-pipeline due to serialization of
{send_to:[pipeline_name]}
.Checklist
Author's Checklist
How to test this PR locally
Run Logstash with pipeline-to-pipeline
upstream.conf
downstream.conf
bin/logstash -f /path/to/p2p/dir/
curl "localhost:9600/_node/stats"
Related issues
Use cases
Screenshots
Logs