You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I am worried that if I adopt this product, it won't scale well in high traffic. I would want to be able to have multiple node servers handling requests in a round-robin fashion, hosted on a fleet of containers. But from what I gather from looking at the docs and code, this isn't possible. If I run multiple instances, I think I'd be running multiple collectors, which would duplicate metrics.
Describe the solution you'd like
I would like to be able run the server in "view only mode", and disable metric collection. This way, I can run one metric collector, and leave the rest of the instances as view only, so that I can scale out new instances to meet traffic needs.
Describe alternatives you've considered
modify the source code myself,
simply have 1 instance and hope it handles traffic load,
simply have many instances, and don't care that the metrics are duplicated. This would mean that different users may have a slightly different metric reporting experience.
Additional context
I think this project is awesome! I would love to adopt it for my use case :)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I am worried that if I adopt this product, it won't scale well in high traffic. I would want to be able to have multiple node servers handling requests in a round-robin fashion, hosted on a fleet of containers. But from what I gather from looking at the docs and code, this isn't possible. If I run multiple instances, I think I'd be running multiple collectors, which would duplicate metrics.
Describe the solution you'd like
I would like to be able run the server in "view only mode", and disable metric collection. This way, I can run one metric collector, and leave the rest of the instances as view only, so that I can scale out new instances to meet traffic needs.
Describe alternatives you've considered
Additional context
I think this project is awesome! I would love to adopt it for my use case :)
The text was updated successfully, but these errors were encountered: