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

Add "How to monitor a signer" #1660

Merged
merged 3 commits into from
Oct 18, 2024
Merged

Conversation

aldur
Copy link
Contributor

@aldur aldur commented Oct 18, 2024

No description provided.

@aldur aldur requested a review from a team as a code owner October 18, 2024 12:20

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
Copy link
Contributor

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...

Copy link
Contributor Author

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.

Copy link
Contributor

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.

@wileyj
Copy link
Contributor

wileyj commented Oct 18, 2024

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.

@wileyj wileyj merged commit f6abd61 into stacks-network:master Oct 18, 2024
4 checks passed
@aldur
Copy link
Contributor Author

aldur commented Oct 21, 2024

@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

@wileyj
Copy link
Contributor

wileyj commented Oct 21, 2024 via email

@aldur
Copy link
Contributor Author

aldur commented Oct 21, 2024

I actually had to fix it: #1662

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

Successfully merging this pull request may close these issues.

2 participants