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

feat: forester alerts + monitoring #1095

Merged
merged 1 commit into from
Aug 29, 2024
Merged

Conversation

sergeytimoshin
Copy link
Contributor

@sergeytimoshin sergeytimoshin commented Aug 18, 2024

Added:

• Tracing-based telemetry
• Prometheus metrics sender
• Prometheus + AlertManager + PushGateway + Grafana docker-compose configuration

@sergeytimoshin sergeytimoshin force-pushed the sergey/forester-tracing branch 2 times, most recently from 1ab8249 to 54428b5 Compare August 26, 2024 03:59
@sergeytimoshin sergeytimoshin changed the title feat: forester tracing feat: forester alerts + monitoring Aug 26, 2024
@sergeytimoshin sergeytimoshin marked this pull request as ready for review August 26, 2024 15:57
@sergeytimoshin sergeytimoshin force-pushed the sergey/forester-tracing branch from 6af6b71 to 0ef25e8 Compare August 27, 2024 17:51
@sergeytimoshin sergeytimoshin marked this pull request as draft August 27, 2024 17:51

Unverified

The committer email address is not verified.
• Prometheus metrics sender
• Prometheus + AlertManager + PushGateway + Grafana configuration
@sergeytimoshin sergeytimoshin force-pushed the sergey/forester-tracing branch from 0ef25e8 to f796c2d Compare August 29, 2024 09:30
@sergeytimoshin sergeytimoshin marked this pull request as ready for review August 29, 2024 09:30
@@ -22,7 +20,71 @@ services:
- PGADMIN_DEFAULT_PASSWORD=photon
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we make this an env variable?
(Same question for postgres login above.)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes we can, and probably should, it's just a default test value, it implies that the end user should replace it with something more secure

ports:
- "3000:3000"
environment:
- GF_SECURITY_ADMIN_PASSWORD=admin
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

env variable necessary?

queue_metric_update(epoch_info.epoch, num_tx_sent, chunk_duration).await;

// TODO: consider do we really need WorkReport
self.increment_processed_items_count(epoch_info.epoch, num_tx_sent)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see that we could use it to push things to graphana but in once we have multiple foresters by different parties we should get the performed work from the ForesterEpochPdas and the total performed work from the EpochPda .

@@ -345,6 +361,7 @@ impl RpcConnection for SolanaRpcConnection {
}

async fn get_slot(&mut self) -> Result<u64, RpcError> {
println!("Calling get_slot");
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't we call info! here?

@ananas-block ananas-block merged commit 89e08a0 into main Aug 29, 2024
21 checks passed
@ananas-block ananas-block deleted the sergey/forester-tracing branch August 29, 2024 18:08
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.

None yet

2 participants