Advanced Search
Search Results
1071 total results found
1.1 Accessing the FileWave Dashboard
What Your account will need permission to access the FileWave Dashboard. When/Why There are three permission levels for the dashboard for each admin logon: No Access Read-Only Access Read-Write Access The permissions are defined with the following o...
1.2 Default Dashboard
What When you open the dashboard, FileWave shows the default system dashboard: When/Why The default dashboard, FileWave System, gives you a quick health view of core FileWave services and configuration items. Green widgets indicate healthy or configured items...
1.3 FileWave Provided Dashboards
What FileWave includes several default dashboards. Some are useful for day-to-day admin checks, while others give FileWave Support a faster view into system health. When/Why Use these dashboards as reporting examples and starting points. They show common ways ...
1.4 Switching Between Dashboards
What Use dashboards to move between FileWave data views after you log in. When/Why Different dashboards show different slices of FileWave data. You can open dashboards in separate browser tabs, switch views in one tab, or use a playlist to cycle through dashbo...
1.5 Dashboard Panel/Widget Layout
What Dashboard panels/widgets can be moved and resized so the dashboard shows the most useful information first. When/Why After you copy or add dashboard content, adjust the layout so related panels sit together and high-priority panels are easy to see. How Dr...
1.6 Exposing an Association to Dashboard
What FileWave can expose an association to the Dashboard so deployment progress is visible as a Dashboard widget. When/Why Use this when a rollout is important enough that administrators or other stakeholders need a quick progress view. It is most useful for l...
2.1 Creating Your Own Dashboard
What FileWave dashboards can be customized. You can start with the included dashboards, then build your own views for the data your team checks most often. When/Why Dashboard elements, also called widgets, can be combined into custom dashboards. You can copy w...
2.2 Copying Widgets (Panels)
What Copy an existing Grafana panel, called a widget in this KB series, when another dashboard already has the view you need. When/Why This is useful when a panel already has the right query, visualization, or layout and you want to reuse it in a custom dashbo...
2.2.1 Copied Panel is Blank
What If a copied dashboard panel is blank, recreate the variables that the panel expects in the destination dashboard, then save the dashboard and reload the panel. When/Why This most often happens when the source dashboard has variables that the panel depends...
2.3 Widget/Panel Elements
What All panels (or widgets) on the FileWave dashboard are comprised of the same basic elements. This article reviews those elements at a high level. When/Why If you are using pre-existing panels, you won't care too much about how they are built. However,...
2.4 Creating a New Panel (existing data)
What Dashboard panels can use existing FileWave Inventory Reports (formerly Queries) as their data source. The panel uses the report rows directly, so this method is best for table panels and does not aggregate values. When/Why Use this when a report already s...
3.1 Aggregating Data
What The FileWave dashboard can show raw device data, but aggregated data is what gives you the quick summary. Aggregation rolls many records into something easier to read, such as counts by version, model, or status. When/Why Use aggregation when you need the...
3.1.1 Grouping Data Using Prometheus
What In order to do summary reporting, we need to leverage the power of Prometheus. When/Why Anytime we want to do something like report on a rollout or general status, we are going to want to summarize a report. We will accomplish this by using a Promethe...
3.1.2 Testing the Prometheus Scrape
What If a scrape target does not appear in Grafana, first check whether Prometheus can see the job and whether the scrape is failing. When/Why Prometheus exposes a targets page that shows the status of configured scrapes. That page is the quickest place to che...
3.1.3 "Exploring" Your New Aggregate Data
What Before you build a formal Grafana panel, it often helps to look at the aggregated data directly. The Explore view is the fastest way to sanity-check what your report is producing. When/Why Use Explore after you have configured the Prometheus scrape and wa...
3.1.4 Creating your Data Panel
What Once your aggregated metric is available in Grafana, you can turn it into a panel that answers the question you actually care about. When/Why Pick the visualization based on the story the data needs to tell. Pie charts work well for a current distribution...
3.2 Extra Metrics
What We learned in the 3.1 section how to build our own custom panels. "Extra Metrics" is an independently built tool to automate creation of a few reporting elements for us without doing it manually. This solution is NOT directly supported by FileWave, but...
4.1 Grafana Email Configuration
What Use this process to configure email in Grafana so alert notifications can be sent by email. When/Why Configure email before you create or test alert notifications. How Edit the Grafana configuration file on the FileWave Server: /usr/local/etc/filewave/gra...