Self Service Report Microservice

The self service report microservice included in your environment, when enabled, supports a number of self service analytics capabilities. To support these features, keep some performance details in mind.

• Self Service Reports: Users with appropriate permissions can create, edit, and send self service reports. If enabled, users can schedule and send reports to other users, or add them to a designated SFTP location.

  • Generate, export, and schedule delivery of PDF reports in a variety of page size and orientation formats.

  • Generate, export, and schedule delivery of reports in Excel (XLSX) format. These reports can include and support formatting and conditional formatting.

• Table visuals: Users with appropriate permissions can export table visuals in Excel (XLSX) format. These visuals can include and support formatting and conditional formatting.

Environment Configuration

Before you enable the self service report microservice in production, work with your infrastructure team to provision appropriate resources. The microservice requires dedicated memory allocation and can scale with additional pods to accommodate concurrent user load and report complexity.

Performance Considerations

Report generation and export performance varies significantly based on report complexity and export format. The following guidelines are provided to help you plan your deployment and use.

Performance expectations noted here are based on internal testing we performed across three report service pods. Your results may vary based on resource allocation and concurrent user load.

In general, test your typical use report configurations thoroughly before deploying at scale.

Report Type Performance

• Simple grouped reports are the best performers across both PDF and Excel (XLSX) formats.

• Simple reports perform well in PDF format; response times increase substantially with more complex datasets. XLSX is more resilient than PDF for simple reports.

• Structured reports are the most resource-intensive type. XLSX exports for structured reports average a few minutes and are not recommended for high-throughput or user-facing scenarios.

Conditional Formatting

Conditional formatting increases generation time significantly. A report with conditional formatting can take from twice as long to significant longer than an equivalent report without it. Conditional formatting on complex reports in PDF format places a higher load on the system, resulting in a percentage of error rates.

File Size and Media

Keep in mind when designing your reports the limitations we built in to optimize performance, and guidelines users should follow for designing and formatting their reports.

• Generated report file size is capped at 50 MB.

• Keep header and footer images in the 200 KB–500 KB range.

Landscape Orientation Considerations

• Reports generated in landscape orientation accommodate more columns per page. This requires additional write operations and memory allocation when compared to portrait, and can result in measurable performance impact.

• Due to the increased demands of landscape oriented reports, test landscape configurations in your environment before you deploy them to production.

• Landscape orientation combined with conditional formatting brings the highest load. Explore alternative configurations or expand the resources available to the self service report microservice.

Scheduling and Distribution

When you enable scheduled reports for your users, keep these operational limits in mind.

• Scheduled reports should be limited to a maximum of 10 recipients per report. Leave adequate time gaps between consecutive scheduled runs.

• Stagger report schedules to avoid concentration of export operations during the same time window.