Template & Data Setup

Learn how to configure dashboards, data granularity, and retention settings in MN Logz Analytics.

Template & Data Setup is the configuration hub of MN Logz Analytics. In this section, users decide which dashboards to enable, how frequently data should be aggregated, and how long it should be retained. This process builds a customized data pipeline for each customer — hosted on an isolated database, secured under a private domain, and visualized via a dedicated Grafana instance.

All configurations created here directly affect database size, cost, and dashboard performance — choose parameters that fit your traffic volume.

What is a Template

A Template is a predefined set of dashboards designed for specific analytics use cases. Templates simplify the onboarding process by grouping related dashboards and default configurations for retention and granularity.

Template Type	Description	Included Dashboards
Basic Analytics	General traffic and performance overview.	Overview, Performance
Request-Based Analytics	HTTP, Cache, and request-level insights.	HTTP, Cache, Access Logs
Full Analytics Suite	Comprehensive dashboard package.	All dashboards
Custom	User-defined dashboards, retention, and granularity.	User-selected

If unsure, start with Basic Analytics — it provides the essential dashboards and can be expanded later.

Request-Based Analytics

Configuration Process

Each template defines three key parameters that determine how your analytics system operates.

The dark theme is already available in the current MN Logz Analytics interface.

1. Dashboards

Choose which dashboards you want to include in your analytics suite: Overview, Performance, HTTP, Cache, or CDN Access Logs.

Disabling unnecessary dashboards reduces storage consumption and improves query performance.

2. Time Granularity

Decide how frequently data should be aggregated — for example, per minute, hour, or day. Shorter intervals provide more precision but increase dataset size.

Retention & Time Granularity

Use hourly granularity for high-traffic sites and daily for moderate traffic to balance performance and cost.

3. Data Retention

Specify how long data should remain accessible — from 7 days up to 12 months, depending on your plan.

Longer retention increases storage cost and may impact query speed on large datasets.

Go to Instance Deployment to launch your MN Logz Analytics instance using this configuration.

Retention & Time Granularity

Why This Page Exists

Every organization has unique traffic behavior, performance goals, and data lifecycle needs. This page allows users to define:

• Which dashboards they want to enable.

• The data granularity (detail level).

• The retention period (historical depth).

• Whether to include Raw / Unprocessed Logs for deep analysis.

Once confirmed, MN Logz Analytics automatically provisions:

• A dedicated database,

• A private domain, and

• A standalone Grafana instance for that user.

This automated process ensures high performance, data isolation, and security for every customer environment.

FAQ

Can I change my template after setup? Yes. You can update or switch templates anytime from the Medianova Control Panel — changes are applied during the next data sync cycle.

How does retention affect cost? Higher retention means more storage and higher cost. The Medianova Control Panel displays estimated cost changes when modifying retention settings.

What happens if I enable all dashboards? Your instance will automatically scale its database capacity, ensuring performance remains stable across larger datasets.