Chore: logs pipelines cover all available processors with tests

[raj-k-singh]

Summary

Adds an explicit happy case test for each pipeline processor that doesn't already have one.
This is in preparation for the work of making pipeline collector config sync by generating transformprocessor based collector config instead of logstransformprocessor based collector config

Related Issues / PR's

Contributes towards #4444

Summary by CodeRabbit

• Refactor
  • Streamlined the codebase by removing unused imports and obsolete test functions.
• Tests
  • Added test cases for various log data processing techniques, enhancing the reliability of log parsing functionalities.

[coderabbitai]

Walkthrough

The recent updates streamline the query-service by removing outdated elements and enhancing testing capabilities for log parsing processors. Unused imports and an obsolete test function were eliminated, simplifying the codebase. Meanwhile, comprehensive tests for various log data manipulation techniques were introduced, ensuring robust functionality across different parsing and processing methods.

Changes

Files	Change Summaries
pkg/query-service/app/logparsingpipeline/preview_test.go	Removed unused imports and deleted the TestTraceParsingProcessor function along with its logic.
pkg/query-service/app/logparsingpipeline/processors_test.go	Added tests for regex_parser, grok_parser, json_parser, trace_parser, add, remove, copy, and move processors.

🐇✨
In the warren, beneath the moon's soft glow,
We pruned the old, for the new to grow.
Across the fields of code, we hop with glee,
Celebrating the changes, free and spree.
🌱🎉

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 8

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 824d9aa and 49ed764.

Files selected for processing (2)

• pkg/query-service/app/logparsingpipeline/preview_test.go (3 hunks)
• pkg/query-service/app/logparsingpipeline/processors_test.go (1 hunks)

Files skipped from review due to trivial changes (1)

• pkg/query-service/app/logparsingpipeline/preview_test.go

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between e977963 and fd2de13.

Files selected for processing (2)

• pkg/query-service/app/logparsingpipeline/preview_test.go (3 hunks)
• pkg/query-service/app/logparsingpipeline/processors_test.go (1 hunks)

Files skipped from review as they are similar to previous changes (2)

• pkg/query-service/app/logparsingpipeline/preview_test.go
• pkg/query-service/app/logparsingpipeline/processors_test.go

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between fd2de13 and a8349ca.

Files selected for processing (1)

• pkg/query-service/app/logparsingpipeline/processors_test.go (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• pkg/query-service/app/logparsingpipeline/processors_test.go