cacti
cacti copied to clipboard
Cacti
Aggregate graph does not adjust CDEF appropriately
Describe the bug
If you have a graph with multiple fields on the data source, then use a CDEF referring to field a and b of that data source, the CDEF will work find with the graph. However, if you then aggregate multiple graphs using the same CDEF, the CDEF is not properly adjusted to cope with multiple graphs, resulting in a bad CDEF.
Switching between Totals Only and All Items, plus Similar Data Sources and All Data Sources can highlight the issue when you look at the graph debug.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@TheWitness Will this fix in v1.2.21 also resolve 95th percentile calculation issues ?
You have to be more specific this ticket was closed automatically by the GitHub bot.
More specific about what? the question was whether the original issue was fixed, and I don't believe that it was. The aggregate functions don't probably adjust CDEF names when being used in multiple items.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@iskandarbasman, two things:
- Don't poach another ticket for your issue, no they are not the same
- Start at the forums and then come here.
@iskandarbasman, two things:
1. Don't poach another ticket for your issue, no they are not the same 2. Start at the forums and then come here.
Hmm.. "no they are not the same issue. Please start a new ticket." would have probably put the same message across.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.