fix(cascadingfilterprocessor): prevent overriding metrics in cascading filter processor - add processor tag

[dmolenda-sumo]

When two cascading filter processor instances were running on one collector, the metrics values were overridden. Adding the instance_name tag fixes this issue

[sumo-drosiek]

I think it should be named processor

[sumo-drosiek]

Also please rename all Instance variables to Processor

[sumo-drosiek]

Please use conventional commits (at least as PR name, so it will be used while squashing and merging) and also please make Ci to be happy 🤗

[swiatekm]

Please use conventional commits (at least as PR name, so it will be used while squashing and merging) and also please make Ci to be happy 🤗

We should just enable https://github.com/zeke/semantic-pull-requests in this repo, just as we have in the Helm chart one.

[swiatekm]

Two requests:

1. I think this should have a changelog entry.
2. Can you squash your commits into one?

LGTM otherwise.

[pmalek-sumo]

Do we want to keep this type of links (i.e. #539 which wouldn't work outside of Github vs embedded markdown links [#539][#539]) ?

@SumoLogic/open-source-collection-team ?

[swiatekm]

I'd personally prefer normal MD links that will work locally as well.

[dmolenda-sumo]

@SumoLogic/open-source-collection-team Do you have any idea what is wrong with the check: PRs checks / markdown-link-check (pull_request)? How to fix this?

[pmalek-sumo]

@SumoLogic/open-source-collection-team Do you have any idea what is wrong with the check: PRs checks / markdown-link-check (pull_request)? How to fix this?

It seems its a known issue with the latest version: gaurav-nelson/github-action-markdown-link-check#127

Let's try to rerun it, it should work just fine as v1 was pinned to previous working version (1.0.13 instead of broken 1.0.14)

[swiatekm]

I reran the link check and it passed. @dmolenda-sumo you just need to rebase on main and we should be good to merge.