Skip to content

Conversation

@wcy-fdu
Copy link
Contributor

@wcy-fdu wcy-fdu commented Feb 18, 2022

What's changed and what's your intention?

PLEASE DO NOT LEAVE THIS EMPTY !!!

Please explain IN DETAIL what the changes are in this PR and why they are needed:

  • Summarize your change (mandatory)
    AWS-S3 provides CloudWatch and X-Ray for monitoring, this PR add aws-s3 monitoring in risingwave grafana dashboards, and s3 dashboards are as follows:

image

  • How does this PR work? Need a brief introduction for the changed logic (optional)
  • Describe clearly one logical change and avoid lazy messages (optional)
  • Describe any limitations of the current code (optional)

Checklist

  • I have written necessary docs and comments
  • I have added necessary unit tests and integration tests

Refer to a related PR or issue link (optional)

#326

@wcy-fdu wcy-fdu requested review from MrCroxx, skyzh and twocode February 18, 2022 07:06
@github-actions github-actions bot added the type/feature Type: New feature. label Feb 18, 2022
let json_context = fs::read_to_string(&s3_dashboard_path)?;
fs::write(&s3_dashboard_path, json_context)?;
let yml = format!(
r#"# --- THIS FILE IS AUTO GENERATED BY RISEDEV ---
Copy link
Contributor

Choose a reason for hiding this comment

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

IIRC, Grafana yaml supports one yaml for multiple dashboards. No need to create two different yaml. You may merge this with the above function.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We hope that risingwabe and third-party service(s3, ec2) on the different dashboards, whereas a grafana yml file corresponding to a dashboards

Copy link
Contributor

@skyzh skyzh Feb 18, 2022

Choose a reason for hiding this comment

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

A grafana yaml file can correspond to multiple dashboards. Anyway, I'm okay with the current approach.

.to_string_lossy()
.to_string();

let json_context = fs::read_to_string(&s3_dashboard_path)?;
Copy link
Contributor

Choose a reason for hiding this comment

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

There should be a fs::copy function?

@codecov
Copy link

codecov bot commented Feb 18, 2022

Codecov Report

Merging #413 (5d52ef5) into main (73765f7) will decrease coverage by 0.00%.
The diff coverage is n/a.

Impacted file tree graph

@@             Coverage Diff              @@
##               main     #413      +/-   ##
============================================
- Coverage     72.91%   72.91%   -0.01%     
  Complexity     2686     2686              
============================================
  Files           867      867              
  Lines         48898    48898              
  Branches       1579     1579              
============================================
- Hits          35655    35653       -2     
- Misses        12430    12432       +2     
  Partials        813      813              
Flag Coverage Δ
java 62.34% <ø> (ø)
rust 77.43% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
rust/meta/src/hummock/compaction.rs 69.53% <0.00%> (-0.67%) ⬇️
rust/common/src/types/ordered_float.rs 25.49% <0.00%> (-0.34%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 73765f7...5d52ef5. Read the comment docs.

@BugenZhao BugenZhao merged commit 0b3a5cf into main Feb 18, 2022
@BugenZhao BugenZhao deleted the wcy_add_s3_dashboards branch February 18, 2022 08:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type/feature Type: New feature.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants