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

Move targetType (empty, raw, event, metric) from runtime / service level to pipeline #1615

Open
SynchronicIT opened this issue Sep 12, 2024 · 0 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@SynchronicIT
Copy link

🚀 Feature Request

Currently all pipelines of an application service use the same targetType. For services which gather both data / events and metrics, or raw / objects and events, etc. etc.

Relevant Package [REQUIRED]

Services which gather both raw, events and/or metrics. E.g a user interface application which make use of both real-time data. (instead of using polling).
Preferable the objects which are generated and/or parsed in other services are forwarded with minimal overhead, thus the raw targetType is preferred.
A combination of events and metric are perhaps more straightforward example.

Description [REQUIRED]

Add an extra parameter to AddFunctionsPipelineForTopics(..) and SetDefaultFunctionsPipeline(..). This could also be in the configuration file as part of the Trigger subject.
The service.runtime code should use the targetType stored at the pipeline instead of the global location in the service.runtime

Describe the solution you'd like

Describe alternatives you've considered

Using Event wrappers, which gives a lot of unneeded overhead and the need to create profiles for all kinds of objects

@SynchronicIT SynchronicIT added the enhancement New feature or request label Sep 12, 2024
@github-project-automation github-project-automation bot moved this to New Issues in Technical WG Sep 13, 2024
@cloudxxx8 cloudxxx8 added the help wanted Extra attention is needed label Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
Status: New Issues
Development

No branches or pull requests

2 participants