Skip to content

Conversation

kaisecheng
Copy link
Contributor

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]}.

A gauge metric of an unknown type (org.jruby.specialized.RubyArrayOneObject) has been created for key: send_to. This may result in invalid serialization.  It is recommended to log an issue to the responsible developer/development team.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files (and/or docker env variables)
  • I have added tests that prove my fix is effective or that my feature works

Author's Checklist

  • test locally

How to test this PR locally

Run Logstash with pipeline-to-pipeline

upstream.conf

input { 
  stdin { }
} 
output { 
    pipeline { 
        send_to => [tube] 
    } 
}

downstream.conf

input { 
    pipeline { 
        address => tube 
    } 
} 
output { 
    stdout { }
}
  1. start logstash
    bin/logstash -f /path/to/p2p/dir/
  2. warning should not emit
  3. check metrics API. No error or missing part.
    curl "localhost:9600/_node/stats"

Related issues

Use cases

Screenshots

Logs

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-actions
Copy link
Contributor

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@mergify
Copy link
Contributor

mergify bot commented Jun 20, 2025

This pull request does not have a backport label. Could you fix it @kaisecheng? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
  • If no backport is necessary, please add the backport-skip label

@elastic-sonarqube
Copy link

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

History

@andsel andsel self-requested a review June 23, 2025 10:53
Copy link
Contributor

@andsel andsel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kaisecheng kaisecheng added the backport-active-all Automated backport with mergify to all the active branches label Jun 23, 2025
@kaisecheng kaisecheng merged commit 909d66c into main Jun 23, 2025
10 checks passed
@kaisecheng kaisecheng deleted the add_list_gauge branch June 23, 2025 12:23
@github-actions
Copy link
Contributor

@Mergifyio backport 8.17 8.18 8.19 9.0

@mergify
Copy link
Contributor

mergify bot commented Jun 23, 2025

backport 8.17 8.18 8.19 9.0

✅ Backports have been created

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)
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)
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 <[email protected]>
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 <[email protected]>
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 <[email protected]>
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 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-active-all Automated backport with mergify to all the active branches

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Warning in logs => A gauge metric of an unknown type (org.jruby.specialized.RubyArrayOneObject) has been created for key: send_to

3 participants