cacti 1.2.26 regarding template naming issues! After creating a new template, the name of the created graphic template has not changed!
In order to solve the problem that the cacti 1.2.26 aggregation template only counts out 95th and not in 95th, I copied the graphics template interface-Traffic (bit/sec, 95th) to a new template and renamed it, but when creating it for the device interface, Two duplicate templates appeared, and the names were the ones I just copied and created, not the names I renamed! Is this something I didn't set up? Or is it a bug?
Thank you so much! Looking forward to your reply!
So do i.
So do i.
We all gave the templates the same name. I copied the new one directly before naming it, so my problem is worse than yours, and renaming it is useless! It can only be the name automatically generated after copying! Ha ha
So do i.
I created the new interface graph template because CACTI 1.2.26 changed the default aggregation template to the 95th way for incoming and outgoing traffic, and the 1.2.26 default aggregation template removed the 95th statistics for incoming traffic, although the developers in the code Fixed this problem and turned it into the 95th sum of the incoming and outgoing directions, which is not what I want. I am more afraid that the developers will definitely do this in version 1.2.27. I am worried that my suggestion will cause more trouble, so I restored the code of 1.2.26 and created a new graphic template to statistically display the 95th of inbound and outbound traffic. That was enough to achieve my purpose.
So do i.
We all gave the templates the same name. I copied the new one directly before naming it, so my problem is worse than yours, and renaming it is useless! It can only be the name automatically generated after copying! Ha ha
Yes, because that's what I'm trying to achieve.😂
So do i.
I created the new interface graph template because CACTI 1.2.26 changed the default aggregation template to the 95th way for incoming and outgoing traffic, and the 1.2.26 default aggregation template removed the 95th statistics for incoming traffic, although the developers in the code Fixed this problem and turned it into the 95th sum of the incoming and outgoing directions, which is not what I want. I am more afraid that the developers will definitely do this in version 1.2.27. I am worried that my suggestion will cause more trouble, so I restored the code of 1.2.26 and created a new graphic template to statistically display the 95th of inbound and outbound traffic. That was enough to achieve my purpose.
In fact, I'm experiencing the same problem as the issue#5689 you created because of version 1.2.26. Before updating lib/api_aggregate.php, the 95th line only existed as outbound even if the inbound value was greater than the outbound. but after updating the code, the 95th line of the 2-port aggregate graph disappeared and the 95th Percentile value below the graph was summing in+out. line disappeared and the 95th Percentile value below the graph summed in+out. so i am also looking for a solution and also creating in&out 95th is not an ideal solution, that's why i will create the graphs template with the same name as yours!
I saw some feedback here that cacti graphics cannot display multiple 95ths. The developer may have changed the calculation method of the aggregation template for this reason.
Our problem is quite awkward. Cacti is global, and in some regions, the 95th percentile value is calculated by summing inbound and outbound traffic, while here it is calculated based on the higher value.
The picture shows the effect of changing the template. The first traffic graph shows the values of inbound and outbound 95 respectively. The third traffic graph is the original 1.2.26 state, with only the value of outbound 95.
To address the issue of Cacti 1.2.26 only calculating outbound but not inbound for the 95th percentile values, I added items 14 and 15 to the graph template and selected them in the Inbound Data Source. I found that the aggregated graph can display outbound and inbound values properly, but the Interface - Traffic graph for individual interfaces still shows combined inbound and outbound values. This might be due to the way the original template handles statistics. If that's the case, I recommend modifying the aggregation template code to follow separate statistical principles.
The 95th percentile values for outbound and inbound are displayed correctly in the aggregated graph
On the original template, the individual interface is not displaying correctly again. The inbound and outbound values are the same...
I suggest that the statistical method of 95th should be restored to the state before version 1.2.25. According to the inbound and outbound of the graph, the 95th should be displayed in a higher direction
So, what is the request here? I'm confused.
Okay, I get it now. Yea, the fact that it's labeled "in + out" makes it very confusing. I'll have to think about this one.
Okay, I get it now. Yea, the fact that it's labeled "in + out" makes it very confusing. I'll have to think about this one.
You misunderstood what I meant. The first post of the main body reflected a bug in the code, that is, there was no way to change the name of the graphic template I created! Thanks
The translator is not very accurate!
So, what is the request here? I'm confused.
When I created a new template and created a monitoring chart on the device, I found two more templates when I selected the template, and changing the name of the template did not take effect! This is what the theme wants to express!
You need to edit the underlying Data Query which is where the title in the Graphs new interface comes from. So, it's a minor training issue.
Also, I get you, which is why I was confused too. There appeared to be multiple issues in this ticket.
Also, I get you, which is why I was confused too. There appeared to be multiple issues in this ticket. There are indeed multiple problems. The bottom one is that the 1.2.26 aggregation template has an error in the parameter definition of the Max 95 value. I changed it to the agg parameter and it worked fine. The original MAX parameter can be counted as inbound. To obtain the value of 95, the AI must first be changed to the agg parameter.
I'm going to close this one. If there is still an issue, please open a separate request.
So do i.
So do i.