-
-
Notifications
You must be signed in to change notification settings - Fork 107
Provide capability to scale Promitor to multiple instances #1450
Copy link
Copy link
Open
Labels
agents:discovery-agentAll issues related to the resource discovery agentAll issues related to the resource discovery agentagents:scraperAll issues related to the scraping agentAll issues related to the scraping agentdeploymentAll issues related to deploying PromitorAll issues related to deploying PromitorfeatureAll issues that are new featuresAll issues that are new featuresintegration:azure-monitorAll issues related to Azure Monitor integrationAll issues related to Azure Monitor integrationintegration:azure-resource-graphAll issues related to Azure Resource Graph integrationAll issues related to Azure Resource Graph integrationruntimeAll issues related to our runtimeAll issues related to our runtime
Description
Metadata
Metadata
Assignees
Labels
agents:discovery-agentAll issues related to the resource discovery agentAll issues related to the resource discovery agentagents:scraperAll issues related to the scraping agentAll issues related to the scraping agentdeploymentAll issues related to deploying PromitorAll issues related to deploying PromitorfeatureAll issues that are new featuresAll issues that are new featuresintegration:azure-monitorAll issues related to Azure Monitor integrationAll issues related to Azure Monitor integrationintegration:azure-resource-graphAll issues related to Azure Resource Graph integrationAll issues related to Azure Resource Graph integrationruntimeAll issues related to our runtimeAll issues related to our runtime
Projects
StatusShow more project fields
Proposed
Provide the capability to scale Promitor to multiple instances without having to scrape metrics on every instance.
To avoid that, it should use a small distributed cache across nodes or a distributed memory cache to share the scraped results.