6.3 Dashboards, Boards and Metric Sources: Trends, Its Replacement and Migration
Key Takeaways
- Tanium Trends is deprecated and replaced by Tanium Reporting, with cloud support ending 11 March 2026 and on-premises support ending 20 May 2026, but Trends must not be uninstalled because it still backs some module overview pages.
- Trends panels depend on sources, which are either saved question sources defining a question and its collection timing, or module sources created when a Tanium solution is imported.
- Creating a saved question source creates a saved question named after the source with the string Trends prepended, and a Trends saved question can ask for results from only one sensor.
- Migration converts Trends boards into Reporting dashboards and creates reports named Trends - <source> for saved question sources, but historical data is not migrated.
- After migrating, any Tanium Connect connections that exported Trends boards or sources must be replaced with connections that export the corresponding Reporting dashboards and reports.
6.3 Dashboards, Boards and Metric Sources: Trends, Its Replacement and Migration
Quick overview: Many Tanium environments still contain Trends boards, and a great deal of third-party study material still teaches Trends as the reporting surface. It is not. Tanium Trends is deprecated and has been replaced by Tanium Reporting. An operator needs to recognise Trends objects, understand the source model they are built on, and know that new work belongs in Reporting.
1. Deprecation status: know this before you study Trends
| Deployment | Status |
|---|---|
| Cloud | Trends deprecated; Tanium supported it until 11 March 2026 |
| On-premises | Deprecation took effect 21 May 2025; support continued until 20 May 2026 |
Tanium's guidance is unambiguous: Trends boards that are actively being used should be migrated to Tanium Reporting. A migration wizard is available in the Trends workbench.
[!IMPORTANT] Trends should not be uninstalled. Tanium states that Trends remains in your environment to support some module overview pages and should not be removed until further notice. So an operator will still see Trends in the console, and still needs to understand what it is — while doing new work in Reporting.
2. The Trends object model
Understanding this model is still worth an operator's time, because Reporting inherits its shape and because migrated content carries its fingerprints.
BOARD a collection of panels
|
+-- SECTION a logical divider within a board
|
+-- PANEL one visualisation
|
+-- SOURCE where the panel's data comes from
Panels depend on sources. You must create a saved question source, or select a module source, before you can create a panel that uses it.
The two source types
| Source type | What it is |
|---|---|
| Saved question source | A configuration defining a Trends saved question, how often to issue the question, and when to collect results from endpoints |
| Module source | A configuration defining data that a Tanium solution provides. It validates and aggregates what the solution supplies |
Facts about saved question sources that catch people out
- Every source issues its saved question to all computer groups visible to Trends — not to a group you pick per source.
- Creating a source creates a saved question named after the source, with the string
Trendsprepended. A source namedChassis Typeproduces the saved questionTrends Chassis Type. That convention exists so you can filter for Trends questions in the saved questions and question history tables — and it explains those unfamiliarTrends …entries in Administration > Content > Saved Questions. - A Trends saved question can ask for results from only one sensor. One metric per source.
- When a saved question source uses a multi-column sensor, you choose which column to display.
Facts about module sources
- They are created when you import a Tanium solution.
- You cannot create or edit them, but you can disable them to stop data being stored.
- Access permissions for the solution that provides the data control access to the module source — not a separate Trends permission.
Notice how directly this carries over into Reporting, where module sources are likewise uncreatable, uneditable, and usable only for dashboard charts.
3. Migrating a board to Reporting
The migration converts boards into Reporting dashboards and processes the panels according to their source type.
| Panel source | What migration does |
|---|---|
| Saved question source | Creates a corresponding report in Reporting. Migrated reports follow the naming convention Trends - <source>, matching the original source name |
| Module source | The Tanium solution that provided the source begins sending data to Reporting for the corresponding dashboard panel |
What does not survive
Historical data is not migrated. For dashboard panels that use historical data — an area chart, for example — Reporting starts collecting only when the dashboard is created. A migrated panel may initially display Collecting initial data, and that is expected rather than a fault.
Permissions and follow-up
- Migrating boards and sources requires the Trends export role permission.
- After migration, verify each board: check the dashboard exists, resolve errors, and expand the dashboard to confirm the corresponding Reports were created for saved question sources. Migrated reports can be listed at Data > Reports by selecting the Trends Migrated label.
- Replace any Tanium Connect connections that exported Trends boards or sources with connections that export the corresponding Reporting dashboards and reports. A migration that leaves the old connections in place quietly stops delivering data.
4. Reading a dashboard well
Whether the object is a legacy board or a Reporting dashboard, the interpretation skills from section 5.4 apply.
| Question to ask | Why |
|---|---|
| What is the source? | A saved question source reflects one sensor; a module source reflects what that solution chose to send |
| What is the collection cadence? | Report data collects on a 24-hour cycle; module source intervals vary by solution |
| What population is included? | Sources issue to the computer groups visible to the module, and computer group filters do not apply to module-source charts |
| Is this a snapshot or a trend? | A trending panel that recently started has no history yet, whichever product produced it |
| Did the denominator move? | A step change usually means scope changed, not the world |
5. What to do with what you find
| Situation | Action |
|---|---|
| A Trends board is in active use | Migrate it to Reporting with the wizard, then verify and replace Connect connections |
| A Trends board is unused | Leave it; do not uninstall Trends, which still backs some module overview pages |
| A new reporting requirement arrives | Build it in Reporting — never create new Trends content |
| Study material presents Trends as current | Treat it as out of date, and check the product's own deprecation notice |
| A migrated panel shows "Collecting initial data" | Expected — historical data does not migrate |
What is the current status of Tanium Trends, and what should an operator do about an actively used Trends board?
An operator finds unfamiliar saved questions whose names begin with the word Trends in Administration > Content > Saved Questions. What are they?
After migrating a Trends board, an area-chart panel on the new Reporting dashboard shows 'Collecting initial data'. What has happened?
A team migrated its Trends boards to Reporting but the nightly export to their data warehouse silently stopped. What was missed?