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

Feat: use new logspipelineprocessor for generating logs pipeline collector conf #6080

Conversation

raj-k-singh
Copy link
Collaborator

Summary

Generate collector config for logs pipelines using the new dedicated logs pipeline processor

Related Issues / PR's

completes #4444

Affected Areas and Manually Tested Areas

Logs Pipelines

@github-actions github-actions bot added the enhancement New feature or request label Sep 26, 2024
@raj-k-singh raj-k-singh changed the base branch from develop to feat/logs-filter-suggestions-higher-rank-for-service-and-env September 26, 2024 05:33
@raj-k-singh raj-k-singh force-pushed the feat/use-logspipelineprocessor-in-logs-pipelines-collector-conf branch from 8526f36 to bb86833 Compare September 26, 2024 05:35
Base automatically changed from feat/logs-filter-suggestions-higher-rank-for-service-and-env to develop September 26, 2024 09:56
@raj-k-singh raj-k-singh force-pushed the feat/use-logspipelineprocessor-in-logs-pipelines-collector-conf branch from bb86833 to 99fbd1e Compare September 26, 2024 12:55
@raj-k-singh raj-k-singh force-pushed the feat/use-logspipelineprocessor-in-logs-pipelines-collector-conf branch from 2213342 to 4e600ba Compare September 26, 2024 13:40
@raj-k-singh raj-k-singh marked this pull request as ready for review September 26, 2024 13:40
@raj-k-singh raj-k-singh merged commit e4d1452 into develop Sep 27, 2024
13 checks passed
@raj-k-singh raj-k-singh deleted the feat/use-logspipelineprocessor-in-logs-pipelines-collector-conf branch September 27, 2024 05:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants