22 Feb 2022 01:07 AM - last edited on 17 May 2023 03:57 AM by Michal_Gebacki
Customer installed the extension (V 1.0.3 and then upgrade to V1.0.4) and we see information only at the top of the dashboard while all other tiles are empty
Also when clicking on the links the information is empty, for example instances link
The extension do pull lots of information in terms of metrics (106)
And when look into the tiles its look like the metrics are not set correctly
After rechoosing them
We do see the information
So it looks like a dashboard issue Any suggestions?
BTW cluster version is 234
All the best and stay safe
Solved! Go to Solution.
Can you share with us some screenshots of the following:
Thanks for the prompt answer!
Here it goes:
Let me know if you need any more information
While the second screenshot is not splitting by an entity - I think I found the issue 🙂
The instance name (retrieved by OID 22.214.171.124.126.96.36.199.0) is the only detail that the entire extension topology depends on as it is used to uniquely identify F5 Instances and the objects running on them.
So long as the F5 device responds with values to the metric queries, the metrics will report those results (even though some splittings may be missing) - this is why you can see metrics and their data.
The top row of tiles on the dashboard removes any dimension splitting which is why these tiles also show data.
All other tiles on the dashboard will split the metrics by the primary entity they belong to. Since you're not registerding "F5 Instance name" that all entities depend on, no entities are being created, hence why these tiles are empty and also why the shortcuts send you to empty lists.
Is it possible for you to run an SNMP Get query against this device?
It would be helpful to see what comes back when querying OID 188.8.131.52.184.108.40.206.0
Hi @Radu ,
OK its looks like we are close to the root cause here ....
From extension log its shows that OID 220.127.116.11.18.104.22.168.0 return no value
Do you still need here to check the response from snmp get ?
@Yosi_Neuman- I think it's pretty clear that the OID returns an empty value.
I am now curious, can you split any of these metrics by "device.name" and "device.address" dimensions?
These are normally resolved from a DNS query against the value of that OID (which usually is the FQDN of the F5 if known). I'm curious what values have these been replaced with.
And finally - has anything changed with the F5 device configuration between using v. 1.0.3 and v. 1.0.4 of the extension? It is very strange that this was not causing issues before as the extension has not changed in this regard.
In which of the metric we can find "device.name" or "device.address" dimensions? browse thru several and found none.
So if we will add to the local DNS entry with the F5 ip it will resolve the issue ?
Customer just connect today the extension with version V1.0.3 and saw a message that there is a new version and update it right a way. Information was not shown from the beginning.
I believe that will fix the problem.
You can always check with an SNMP Get against the OID 22.214.171.124.126.96.36.199.0 - as long as this does not return a value, you will not get entities.
device.name and device.address are added automatically to all metrics coming from an extension. If you're not seeing them it means that we don't have any default values, so they depend on the DNS name being resolved correctly.
We will ask to add the DNS entry and will update ASAP
Hi again @Radu
After adding the DNS entry the message regarding the missing DNS disappeared
But still the OID 188.8.131.52.184.108.40.206.0 returns no value
And data is not shown
Any other suggestion what is missing from the F5 side that not return the sysName?
Thanks in advance
Try also restarting the snpmd agent on the F5 (as per f5 recommendation)
And also manually setting it to a value (as per f5 article here)
Working on those suggestions with customer.
Will update ASAP
After restart of the snpmd agent on the F5 we started to see "device.name" and "device.address" dimensions for f5 metrics.
The instance name was added after some inside configuration by the F5 guy and now we see information!!
Thanks for your support !
All the best and stay safe