-
Notifications
You must be signed in to change notification settings - Fork 103
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
v2 - Not able to extend declare block with custom logic #1163
Comments
Let me just make sure I understand the real request. You want to take the podLogs feature (gather logs from all pods) and:
If that sounds right, let me know and I can work on some options for you. |
Absolutely correct, thank you for reviewing this |
@petewall hey, do you have any new info about this? Do I understand correctly that it's required to change helm chart to support this case? thanks |
Yeah, we don't have the ability to add the |
Hey everyone!
We have tried to upgrade helm chart to v2 and faced the issue with impossibility of configuring additional custom logic.
We are using experimental feature
loki.secretfilter
for obfuscation of logs. In helm chart v1 we pasted the following code to make it work:So basically we just reused existing
discovery.relabel.filtered_pod_logs.output
in our custom logic.In v2, it seams like its impossible. The new declare block is closed for any inputs/outputs and we can customise it only by adding new extraDiscoveryRules and extraLogProcessingStages.
We can not add new
loki.process
there or hook into output flow to introduce additional chain:Also we can not use output from declare block to supply the new processing chain somehow:
Could you please review this and let me know you thoughts on that matter?
The text was updated successfully, but these errors were encountered: