-
Notifications
You must be signed in to change notification settings - Fork 238
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
Add "How to monitor a signer" #1660
Conversation
|
||
Once done, access your dashboard, click on "Connections", "Add new connection", | ||
and select "Hosted Prometheus metrics". Select "Via Grafana Alloy", then on step | ||
2 select "Run Grafana Alloy" to generate an API token. Note the token |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this needs a qualifier - if it's not a gcloud hosted service, will the key ids may be different?
By default, grafana will create a hosted instance in gcloud (configurable) - Note the token...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well if using a Prometheus instance not hosted by Grafana, users would need to provide their username/password (or token). But I think that's out of scope for this guide, I want to make it as easy as possible.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, but i think (going off of memory) when you first setup the instance, they give you some options. gcloud being one, aws being another., etc
in your doc, the keys are specific to the gcloud option but i would suspect that if someone chose aws, the key id's may be different.
Looks good to me! i'm not entirely certain how the navigation works though so i'd prefer @kenrogers takes a look before it's merged in case a navigation link needs to be added. |
@kenrogers (or anyone who can), do we need a deployment? I don't see it live here: https://docs.stacks.co/guides-and-tutorials/running-a-signer |
… On Mon, Oct 21, 2024 at 00:29 Adriano Di Luzio ***@***.***> wrote:
@kenrogers <https://github.com/kenrogers> (or anyone who can), do we need
a deployment? I don't see it live here:
https://docs.stacks.co/guides-and-tutorials/running-a-signer
—
Reply to this email directly, view it on GitHub
<#1660 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAVXIHFE5M66YGPGVHHMCKLZ4SUO5AVCNFSM6AAAAABQF2VFYCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRVHA2DGNZTHE>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
I actually had to fix it: #1662 |
No description provided.