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
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):
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
The text was updated successfully, but these errors were encountered:
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):
I have enabled the alertmanager in the cortex config:
when I try to run the cortextool to get the current AlertManager, I get the following output
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
The text was updated successfully, but these errors were encountered: