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

Thold Plugin Issue - Last Value not match with Graph Current Value #702

Open
JasonRaptor opened this issue Oct 4, 2024 · 8 comments
Open

Comments

@JasonRaptor
Copy link

Describe the bug

Hello Sir,

As I am still encountering with this issue, and I am not able to find out the solution for that. The problem I met are as below.

Last Value (Megabytes (MB)) NOT EQUAL TO Graph Current Value (Megabits (Mb))

Even I have use the Last Value x 8, and not match with the Graph Current Value.

Thank you so much.

To Reproduce

Steps to reproduce the behavior:

  1. Go to Thold Page
  2. Select any network interface, and click the "edit threshold" button
  3. Compare the Last Value on the left side and the Graph Current Value on the right side graph

Remarks:
Last Value show as Megabytes (MB)
Graph Current Value: Use with CDEF (Turn Bytes into Bits) (Please take a look at attached)

Expected behavior

A clear and concise description of what you expected to happen.

Screenshots

Threshold not Correct

Graph Template Setting

Cacti and Plugin Version

Cacti - Version 1.2.27
Thold - Version 1.8.1

@TheWitness TheWitness transferred this issue from Cacti/cacti Oct 8, 2024
@xmacan
Copy link
Member

xmacan commented Oct 14, 2024

@JasonRaptor sorry, wrong issue

@xmacan xmacan closed this as completed Oct 14, 2024
@xmacan xmacan reopened this Oct 14, 2024
@JasonRaptor
Copy link
Author

@xmacan Hello Petr, thanks for your checking.

@TheWitness
Copy link
Member

@xmacan and @JasonRaptor, any updates on this?

@xmacan
Copy link
Member

xmacan commented Nov 7, 2024

I have tested it but I don't remember the result. I will try it tomorow

@JasonRaptor
Copy link
Author

Hello, I am still encountering with the issue

@xmacan
Copy link
Member

xmacan commented Nov 17, 2024

@TheWitness - I tried to fix it, but no luck. I don't think I understand something.

@TheWitness
Copy link
Member

Okay

@JasonRaptor
Copy link
Author

Thanks for both of your effort to help on this issue, hope that there will have a solution for that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants