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

Filters in Input Processors do not Emit Metrics #7391

Closed
msolters opened this issue May 15, 2023 · 3 comments · May be fixed by #9341
Closed

Filters in Input Processors do not Emit Metrics #7391

msolters opened this issue May 15, 2023 · 3 comments · May be fixed by #9341

Comments

@msolters
Copy link

Bug Report

Describe the bug
When we move filters inside the processors.logs of a specific input, the api/v1/metrics/prometheus stops emitting metrics for those filters. For example:

    pipeline:
      inputs:
        - name: tail
          alias: foo
          path: $the_paths
          db: /var/log/fluent-bit-s3.db
          db.sync: normal
          db.locking: true
          db.journal_mode: WAL
          key: message
          tag: foo.*
          buffer_chunk_size: 2MB
          buffer_max_size: 5MB
          mem_buf_limit: 50MB
          path_key: log_file_path
          skip_long_lines: On
          offset_key: offset
          storage.type: filesystem
          threaded: on
          processors:
            logs:
              - alias: lua-s3
                name: lua
                match: foo.*
                script: custom_filters.lua
                call: foo_rewrite_for_s3

In this configuration we see no filter metrics for the lua-s3 filter.

Expected behavior
Filters should emit metrics whether or not they are in an input's thread-specific processor stack or not.

Screenshots

Your Environment

  • Version used: v2.1.2
@msolters
Copy link
Author

msolters commented Aug 4, 2023

I have reproduced this on 2.1.8.

Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.

@github-actions github-actions bot added the Stale label Dec 10, 2023
Copy link
Contributor

This issue was closed because it has been stalled for 5 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants