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

Regarding accessing multiple workspaces #70

Open
hgsat123 opened this issue Mar 10, 2022 · 1 comment
Open

Regarding accessing multiple workspaces #70

hgsat123 opened this issue Mar 10, 2022 · 1 comment

Comments

@hgsat123
Copy link

Hi,
I have a created a workspace in a specified AWS region, provided necessary access to IAM role (annotated for a specified service account) to read/write access to this workspace. I'm able to write prometheus scrapped metrics (defined write_relabel_configs) to specified workspace. If i want to write same metrics to different workspace parallelly (mentioned url, sigv4 details of workspace region), prometheus ignores the second workspace though it exist in the same region (as first workspace). I see error - err="server returned HTTP status 404 Not Found: {"Message":"Workspace not found"}" in the prometheus logs.
I also see messages like Stopping remote storage...", Remote storage stopped." for the first workspace. So, prometheus shuts one of the workspace / storage to write WAL only to second one!. Question: Is there a way to write to multiple workspaces parallelly?

@Aneurysm9
Copy link
Member

Hi, can you please provide some more detail so that we can understand your deployment and potential issue? Are you using the OpenTelemetry Collector? If so, can you provide your configuration? I would expect that you could define multiple prometheusremotewrite exporter instances and put them all on the same pipeline to achieve this result.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants