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

Cortextool alertmanager load gives "cortextool: error: requested resource not found, try --help" error #200

Open
geekyspartan opened this issue Jul 20, 2021 · 2 comments

Comments

@geekyspartan
Copy link

I have cortex running locally with the 'fake' tenant/object id.
For testing out the alertmanager, I am using the below dummy config (alertmanager.yml):

global:
  smtp_smarthost: 'localhost:25'
  smtp_from: 'youraddress@example.org'

route:
  receiver: example-email

receivers:
 - name: example-email
   email_configs:
    - to: 'youraddress@example.org'

I have enabled the alertmanager in the cortex config:

alertmanager:
  enable_api: true

alertmanager_storage:
  backend: azure
  azure:
    account_name: ******
    account_key: ******
    container_name: ******
    endpoint_suffix: ******

when I try to run the cortextool to get the current AlertManager, I get the following output

cortextool alertmanager get --address=http://localhost:9009 --id=fake
INFO[0000] no alertmanager config currently exist for this user 

This is fine, as currently I don't have any AlertManager setup, so the output is correct.

Now, if I try to load a AlertManager via this command:
cortextool alertmanager load alertmanager.yml --address=http://localhost:9009 --id=fake

I get the following error:
cortextool: error: requested resource not found, try --help

I am not sure if I have to enable anything else in the cortex or if alertmanager.yml content is wrong.
My assumption is, if I am able to load a dummy alertmanager.yml, then I will be able to atleast open this url: http://localhost:9009/alertmanager

@vinitmasaun
Copy link

I am also facing this issue. @geekyspartan Were you able to resolve this issue? If so, could you please share how you resolved it?

@geekyspartan
Copy link
Author

I am also facing this issue. @geekyspartan Were you able to resolve this issue? If so, could you please share how you resolved it?

Actually, we changed our approach, so didn't work on this issue.

friedrichg pushed a commit to cortexproject/cortex-tools that referenced this issue Aug 1, 2023
Signed-off-by: Tom Hayward <thayward@infoblox.com>
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