Skip to content

Conversation

@Alenar
Copy link
Collaborator

@Alenar Alenar commented Oct 14, 2024

Content

This PR:

  • Harmonize all "function enter" logs message to be in the form of >> function_name.
    • Excepted in the http server where they are in the form of HTTP_VERB /path/to/endpoint.
  • Remove all prefixes previously used to help find the log of a component since they logs are tagged with their source component since Enhance logs construction and usage in aggregator #2002.
  • Capitalize the first letters of all "functional" logs.
  • Move away from the log message into a property huge structure (ie: some logs joined errors into their message, those errors have been moved to a "error" property).

Pre-submit checklist

  • Branch
    • Tests are provided (if possible)
    • Crates versions are updated (if relevant)
    • CHANGELOG file is updated (if relevant)
    • Commit sequence broadly makes sense
    • Key commits have useful messages
  • PR
    • No clippy warnings in the CI
    • Self-reviewed the diff
    • Useful pull request description
    • Reviewer requested

Issue(s)

Relates to #1981

@github-actions
Copy link

github-actions bot commented Oct 14, 2024

Test Results

    4 files  ±0     54 suites  ±0   9m 26s ⏱️ +7s
1 358 tests +6  1 358 ✅ +6  0 💤 ±0  0 ❌ ±0 
1 566 runs  +6  1 566 ✅ +6  0 💤 ±0  0 ❌ ±0 

Results for commit 20156b9. ± Comparison against base commit 8fbaaee.

♻️ This comment has been updated with latest results.

@Alenar Alenar temporarily deployed to testing-preview October 14, 2024 16:26 — with GitHub Actions Inactive
@Alenar Alenar temporarily deployed to testing-sanchonet October 14, 2024 16:26 — with GitHub Actions Inactive
Copy link
Member

@jpraynaud jpraynaud left a comment

Choose a reason for hiding this comment

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

LGTM 🚀

Copy link
Collaborator

@dlachaume dlachaume left a comment

Choose a reason for hiding this comment

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

LGTM 🚀
I've added some additional data to the input logs of the aggregator runner functions. It’s just a suggestion, i'm not 100% sure if it brings real value without cluttering the logs. Also included a few rephrasing suggestions and typo in the HTTP routes logs.

Copy link
Collaborator

@sfauvel sfauvel left a comment

Choose a reason for hiding this comment

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

LGTM

Alenar added 11 commits October 15, 2024 11:55
Since now each logs are tagged with their source component.
Prefix them with a `>> ` followed by the rust function name (including
the `_`) so they can be search easily.
Prefix enter function logs with the http verb followed by the route
path.
And instead add them to a property. This allow to keep the main log
messages leans while still providing detailed errors info.
And write them to an isolated `error` property.
There is a caveat: payload and query strings can't be logs this way, so
in this cas a local "function enter" log is done.
This ensure that those data are logged at the price of routes producing
two logs for one call.
Adjust some logs messages & added properties
* mithril-aggregator from `0.5.82` to `0.5.83`
* mithril-signer from `0.2.199` to `0.2.200`
@Alenar Alenar force-pushed the djo/1981/rework-aggregator-log-msgs branch from 80a4792 to 20156b9 Compare October 15, 2024 09:56
@Alenar Alenar temporarily deployed to testing-preview October 15, 2024 10:04 — with GitHub Actions Inactive
@Alenar Alenar temporarily deployed to testing-sanchonet October 15, 2024 10:04 — with GitHub Actions Inactive
@Alenar Alenar merged commit 0d4d6bc into main Oct 15, 2024
45 of 46 checks passed
@Alenar Alenar deleted the djo/1981/rework-aggregator-log-msgs branch October 15, 2024 11:43
@jpraynaud jpraynaud mentioned this pull request Oct 24, 2024
3 tasks
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.

5 participants