Added support for GAUGE_LIST metric type#17721
Merged
kaisecheng merged 2 commits intomainfrom Jun 23, 2025
Merged
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.
Contributor
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
Contributor
|
This pull request does not have a backport label. Could you fix it @kaisecheng? 🙏
|
|
💚 Build Succeeded
History
|
Contributor
|
@Mergifyio backport 8.17 8.18 8.19 9.0 |
Contributor
✅ Backports have been createdDetails
|
mergify bot
pushed a commit
that referenced
this pull request
Jun 23, 2025
* 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)
mergify bot
pushed a commit
that referenced
this pull request
Jun 23, 2025
* 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)
This was referenced Jun 23, 2025
mergify bot
pushed a commit
that referenced
this pull request
Jun 23, 2025
* 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)
6 tasks
mergify bot
pushed a commit
that referenced
this pull request
Jun 23, 2025
* 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)
6 tasks
kaisecheng
added a commit
that referenced
this pull request
Jun 23, 2025
* 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 <69120390+kaisecheng@users.noreply.github.com>
kaisecheng
added a commit
that referenced
this pull request
Jun 23, 2025
* 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 <69120390+kaisecheng@users.noreply.github.com>
kaisecheng
added a commit
that referenced
this pull request
Jun 23, 2025
* 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 <69120390+kaisecheng@users.noreply.github.com>
kaisecheng
added a commit
that referenced
this pull request
Jun 23, 2025
* 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 <69120390+kaisecheng@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.





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