Znuny Health Check & Performance Tuning
Slow load times or high server load? We optimize database queries, indexing, caching, and daemon workers for noticeably faster response times.
Znuny Statistics with Power BI and BI Reporting
Znuny statistics help you analyze ticket volume, handling times, and service desk distributions. For richer visualizations, export suitable results and prepare them in Power BI, Excel, or another BI tool. This guide describes a conservative, auditable export workflow and does not assume that Znuny provides a native Power BI connector.
Define reporting goals first
Section titled “Define reporting goals first”Before choosing technology, define the decision each report should support. Useful questions include:
- How does ticket volume change by week or month?
- Which queues have the most open or overdue tickets?
- How are types, priorities, or services distributed?
- How long does handling take within the selected period?
Verify the meaning of every field in your Znuny configuration. Dynamic fields, state definitions, and working-time calendars can differ between installations.
Prepare a Znuny statistic
Section titled “Prepare a Znuny statistic”Create or reuse a statistic that contains only the required columns and a clearly defined time range. Access to statistics depends on the permissions assigned to the signed-in agent.
For stable BI reporting:
- Document the time range and filters.
- Keep column names and data types stable.
- Define the time zone and date format.
- Mark or exclude test tickets and internal special cases.
- Export only data the intended audience is allowed to see.
Available export formats depend on the statistic type and Znuny version. A structured CSV export is suitable for Power BI and Excel when the selected statistic offers it.
Import a Znuny CSV into Power BI
Section titled “Import a Znuny CSV into Power BI”- Run the statistic for the required period and save the export.
- In Power BI Desktop, choose Get data, then Text/CSV.
- Verify the delimiter, character encoding, and column headers.
- In Power Query, explicitly set data types for dates, times, and numbers.
- Remove or pseudonymize personal columns that are not required.
- Validate sample records before building measures and visualizations.
Power BI calculates only from the supplied data. Metrics such as response or resolution time must therefore match your calendars, state transitions, and SLA definitions.
Useful helpdesk metrics
Section titled “Useful helpdesk metrics”A first Znuny dashboard might include:
- incoming and closed tickets per period;
- the current number of open tickets;
- distribution by queue, type, priority, or service;
- age bands for open tickets;
- handling or resolution time when the exported data supports a reliable calculation;
- manually corrected classifications when automation is connected.
Avoid metrics without a precise definition. In particular, document start and end events, filters, and how reopened tickets are handled.
Build a repeatable refresh process
Section titled “Build a repeatable refresh process”A manual export is enough for initial analysis. For recurring reports, document the file name, location, schema, and run time. Power BI can read the same file or folder again; scheduled refresh depends on your Power BI environment, any required gateway, and licensing.
If you build a custom integration instead of using files, rely on documented interfaces and limit the service account to required data. Start with the Znuny REST API and web services documentation.
Privacy and quality assurance
Section titled “Privacy and quality assurance”Ticket exports can include names, email addresses, free text, and references to confidential attachments. Minimize personal data, restrict access to exports, and define retention periods. Test changes to statistics or export processes in a Znuny staging system first.
After each change, compare dashboard samples with the source Znuny statistic. This catches incorrect filters, data types, or relationships before the report is distributed.
Related topics
Section titled “Related topics”Summary
Section titled “Summary”Znuny Power BI reporting starts with a well-defined statistic and a controlled export. Stable columns, documented filters, privacy, and data validation matter more than building the most complex possible dashboard.
Frequently asked questions
How can I effectively define reporting goals for Znuny statistics?
To effectively define reporting goals for Znuny statistics, begin by clarifying the specific decisions each report should support. Instead of immediately focusing on technology, identify the business questions you need to answer. For instance, consider how ticket volume changes over time (e.g., weekly or monthly), which queues have the highest number of open or overdue tickets, or how ticket types, priorities, or services are distributed across your helpdesk. It's crucial to verify the precise meaning of every field within your unique Znuny configuration, as dynamic fields, state definitions, and working-time calendars can vary significantly between installations. This foundational step ensures your reports provide actionable insights rather than just raw data.
Quellen / Sources
What are the best practices for preparing Znuny statistics for export to Power BI or Excel?
When preparing Znuny statistics for export, it's essential to create or reuse a statistic that contains only the necessary columns and covers a clearly defined time range. For stable Business Intelligence (BI) reporting, several best practices should be followed. Firstly, meticulously document the time range and any filters applied to the statistic. Secondly, ensure that column names and data types remain stable across exports to prevent issues with your BI tool. Thirdly, clearly define the time zone and date format used in the export. Fourthly, mark or exclude test tickets and internal special cases to maintain data integrity. Lastly, only export data that the intended audience is authorized to see, adhering to privacy guidelines. A structured CSV export is generally suitable for Power BI and Excel, provided the selected statistic offers this format.
Quellen / Sources
How do I import Znuny CSV data into Power BI and ensure data quality?
To import Znuny CSV data into Power BI and maintain data quality, begin by running the desired statistic in Znuny and saving the export file. In Power BI Desktop, select Get data and then Text/CSV. During the import process, carefully verify the delimiter, character encoding, and column headers to ensure correct parsing. The crucial next step is to use Power Query to explicitly set appropriate data types for dates, times, and numbers, as Power BI's automatic detection might not always be accurate. Additionally, remove or pseudonymize any personal columns that are not required for your analysis to comply with privacy standards. Before building measures and visualizations, validate a sample of records to confirm data accuracy and consistency. Remember that Power BI calculates solely from the supplied data, so metrics like response or resolution time must align precisely with your Znuny calendars, state transitions, and SLA definitions.
Quellen / Sources
Which key helpdesk metrics can I track using Znuny statistics and Power BI?
When analyzing Znuny statistics with Power BI, a foundational dashboard often includes several key helpdesk metrics. These typically encompass incoming and closed tickets per period, providing insights into workload and completion rates. Tracking the current number of open tickets is vital for understanding ongoing demand. Distribution metrics, such as tickets by queue, type, priority, or service, help identify bottlenecks and resource allocation needs. Age bands for open tickets are useful for prioritizing and managing overdue items. If your exported data supports reliable calculations, handling or resolution time offers critical performance indicators. Finally, manually corrected classifications can be included, especially when automation is in use, to track data quality. It's imperative to avoid metrics without precise definitions; always document start and end events, filters, and how reopened tickets are handled to ensure accuracy and consistency across reports.
Quellen / Sources
What is the recommended process for establishing a repeatable refresh process for Znuny BI reports?
Establishing a repeatable refresh process for Znuny BI reports is crucial for ongoing analysis. While a manual export suffices for initial insights, recurring reports demand a more structured approach. For file-based reporting, meticulously document the file name, its storage location, the data schema, and the exact run time of the Znuny statistic export. Power BI is capable of reading the same file or folder repeatedly, but scheduled refresh capabilities depend on your specific Power BI environment, any required data gateways, and your licensing tier. If you opt for a custom integration instead of file exports, it's highly recommended to rely on documented interfaces like the Znuny REST API or web services. Furthermore, ensure that the service account used for such integrations is strictly limited to accessing only the required data, adhering to the principle of least privilege.
Quellen / Sources
What privacy and quality assurance considerations are important when working with Znuny data exports?
When working with Znuny data exports, both privacy and quality assurance are paramount. Ticket exports can contain sensitive personal data, including names, email addresses, free text, and references to confidential attachments. To protect this information, you must minimize the collection of personal data, strictly restrict access to the exported files, and define clear retention periods for the data. For quality assurance, it is highly recommended to test any changes to statistics or export processes within a dedicated Znuny staging system before deploying them to production. After each modification, compare samples from your dashboard with the source Znuny statistic. This critical step helps to identify and correct any incorrect filters, data types, or relationships in your BI report before it is distributed to stakeholders, ensuring accuracy and reliability.
Quellen / Sources