search

f5devcentral / application-study-tool

The Application Study Tool provides enhanced insights into (classic) BIG-IP products, leveraging best in class open source telemetry tools
Apache License 2.0
17 stars 6 forks source link

No Data displaying for some LTM's #52

Open powerballad opened 4 days ago

powerballad commented 4 days ago

I have added all my LTM's to the AST. For some of the LTM's, certain dashboards are displaying No data for objects. For example, on the Virtual Servers dashboard, some of the LTM's display virtual server data and some say No data. What would be causing this to happen and are AST logs that would show what the problem is?

clhain commented 4 days ago

Hi there, can you fill out the below information (or if you close this and open a new issue using the bug template, it will autopopulate) - mostly the stuff at the bottom has instructions for grabbing logs and metric output):

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

  1. Go to '...' (Which dashboards / panels it effects. )
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

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

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

Additional context Add any other context about the problem here, including BigIP service account permission level, BigIP Versions.

Attachments If the issue is in regards to missing data in dashboards, please also run the following from the installed host and attach the output:

curl 'localhost:9090/federate?match[]=%7B__name__%3D~"f5.%2A"%7D'

Logs for the collector can be gathered with:

docker logs application-study-tool-otel-collector-1 --tail 1000
mikempw commented 3 days ago

In addition, remember you'll need to be an administrator of the BIG-IP to collect the full stat portfolio. If you have different administrative IDs you'll need to modify the yaml file and designate a user per BIG-IP. For those that may not be familiar, just remember, it's using environmental variables/secrets. So, once the container is started, it will go into memory. I'd highly suggest looking at this: https://f5devcentral.github.io/application-study-tool/config/secret_management/vault_based.html