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: add otel spec #1

Merged
merged 1 commit into from
Jun 24, 2024
Merged

Conversation

alexghr
Copy link
Contributor

@alexghr alexghr commented Jun 13, 2024

No description provided.

- we will use base units for values (e.g. `bytes` over `kilobytes` and `seconds` over `milliseconds`)
- we will _not_ include the unit in the name (there's a separate attribute for that, see code examples)

TBD `meter` naming conventions (ie. `metrics.getMeter('RealPublicKernelCircuitSimulator')`)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Class name seems reasonable to me!

public async publicKernelCircuitSetup(input: PublicKernelCircuitPrivateInputs): Promise<PublicKernelCircuitPublicInputs> {
// ...

this.circuitSimulationMetric.record(duration / 1000, {
Copy link
Collaborator

Choose a reason for hiding this comment

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

duration * 1000

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Sorry, forgot to get back to you on this. The latest recommendation is to use seconds over milliseconds for duration metrics. I've updated the proving code to return a durationMs field instead of the unitless duration we had before.

open-telemetry/opentelemetry-specification#2977

- [ ] AVM
- [x] Sequencer
- [ ] Fees
- [ ] P2P Network
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we plug the metrics into the P2P module? Would be great if we can.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'll look into getting some stats out of it

@alexghr alexghr merged commit d0774d8 into AztecProtocol:main Jun 24, 2024
@alexghr alexghr deleted the alexg/feat/metrics branch June 24, 2024 08:42
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.

3 participants