> ## Documentation Index
> Fetch the complete documentation index at: https://metoro.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Product Updates
> New updates and improvements
Stay up to date with the latest Metoro product updates, new features, platform improvements, and customer-facing fixes.
## On-premises 10.2.0
Metoro on-premises `10.2.0` is now the pinned install and onboarding version for the `10.x` chart line. New hub installs, hub self-monitoring, monitored-cluster onboarding, and operational runbooks now point at the matching `metoro-onprem` and `metoro-exporter-onprem` chart versions.
Existing `10.1.0` hubs can move to the new chart with the [10.1.0 to 10.2.0 upgrade guide](/on-premises/10.x/upgrades/10-1-0-to-10-2-0). Older 10.x hubs should follow the previous 10.x upgrade guides in order before moving to `10.2.0`.
10.2.0 supports the latest telemetry RBACs and Permission CRDs released in Cloud yesterday.
## Metoro Telemetry RBAC and CRDs
Cloud now supports telemetry RBACs. Administrators can now restrict the data that is seen by users by assigning roles with attached telemetry permissions. See [the docs](https://metoro.io/docs/user-management/rbac#telemetry-permissions) for more details.
Cloud now supports permission CRDs. Administrators can now deploy Metoro CRDs to monitored clusters to define both resource and telemetry permission. See [the docs](https://metoro.io/docs/user-management/kubernetes-crds) for more details.
## On-premises 10.1.0
Metoro on-premises `10.1.0` is now the pinned install and onboarding version for the `10.x` chart line. New hub installs, hub self-monitoring, monitored-cluster onboarding, and operational runbooks now point at the matching `metoro-onprem` and `metoro-exporter-onprem` chart versions.
This version also includes alpha support for running direct [PromQL](/metrics/promql) metric queries through a separate PromQL execution engine.
Existing `10.0.2` hubs can move to the new chart with the [10.0.2 to 10.1.0 upgrade guide](/on-premises/10.x/upgrades/10-0-2-to-10-1-0). Existing `10.0.1` hubs should first follow the [10.0.1 to 10.0.2 upgrade guide](/on-premises/10.x/upgrades/10-0-1-to-10-0-2).
## PromQL dashboard queries
[PromQL](/metrics/promql) is now available as an alpha query mode for metric dashboard widgets, making it easier to reuse existing Prometheus and Grafana queries in Metoro. The new docs cover dashboard usage, examples, and current alpha limitations, including possible minor correctness differences from Prometheus and weaker performance than native [MetoroQL](/metrics/metoroql).
## On-premises 10.0.2
Metoro on-premises `10.0.2` is now the pinned install and onboarding version for the `10.x` chart line. New hub installs, self-monitoring, monitored-cluster onboarding, and operational runbooks now point at the matching `metoro-onprem` and `metoro-exporter-onprem` chart versions.
Existing `10.0.1` hubs should follow the [10.0.1 to 10.0.2 upgrade guide](/on-premises/10.x/upgrades/10-0-1-to-10-0-2) before moving to the new chart.
## Reliability defaults
Fair resource sharing is now enabled by default in charted deployments so new installs and upgrades avoid accidentally disabling workload scheduling fairness.
## On-premises 10.x installs
[Metoro Hub 10.x](/on-premises/10.x/overview) now has a customer-facing [standalone Helm chart](/on-premises/10.x/installation/install-hub) for on-premises deployments. The chart uses an on-prem-specific values API, validates common configuration mistakes before install, and supports [bundled or external dependencies](/on-premises/10.x/installation/planning#bundled-or-external-dependencies) without exposing SaaS-only chart options.
* Bundled PostgreSQL now runs on CloudNativePG with operator-managed failover and optional scheduled object-store backups.
* Bundled ClickHouse has production-oriented defaults for startup behavior, disruption protection, Keeper metrics, [hot/cold object storage](/on-premises/10.x/installation/planning#clickhouse-storage), and optional full backups.
* [Monitored-cluster onboarding](/on-premises/10.x/installation/connect-monitored-clusters) can install the pinned on-prem exporter chart directly, including support for ServiceMonitor-based baseline metrics.
* [Trusted CA bundles](/on-premises/10.x/installation/planning#certificate-chains) can be passed through the Hub and exporter charts for private PKI, self-signed endpoints, PostgreSQL TLS, and object-store backups.
## Chart inspection improvements
Chart tooltips are easier to inspect during debugging. You can pin a tooltip by clicking the chart, keep crosshairs aligned across related charts, drag pinned tooltips, filter long tooltip series lists, and distinguish display labels from split/group-by labels more clearly.
## Trace debugging
[Service APM trace feeds](/traces/overview#the-trace-view) now include status controls that make it easier to focus on failures. You can filter traces by available HTTP status codes or OpenTelemetry `statusCode` values, and quickly toggle to error-only traces from the service trace view.
## AI investigation from traces
Error trace details now include a [Guardian](/ai-sre/overview) investigation action that sends the trace context to AI SRE so you can ask what happened from the trace view. [Related logs](/traces/common-questions#how-do-i-view-logs-for-a-specific-trace-or-span) also use the server container and the trace time range, so useful context can appear even when logs do not explicitly contain a trace ID.
## Service map context
[Service map](/traces/service-map) edges now show compact trace-count badges directly on the map, giving connection-volume context without opening the details panel.
## Faster repeated historical queries
Metoro now has an [incremental query response cache](/concepts/incremental-cache) for repeated historical dashboard and explorer queries. Stable long-range metric, log, trace, and Kubernetes queries can reuse previously computed work, making repeat views of historical windows significantly faster once cached.
[Log listing](/logs/overview#log-search-and-performance) also tries a short edge window first when loading the first page of recent logs, then falls back to the full range only when needed. This makes dense log views feel more responsive without changing export behavior.
## AI SRE conversation history
Guardian conversations now get concise chat summaries so new chats are easier to recognize later. [Autonomous investigation](/ai-sre/anomaly-detection) runs are hidden from normal chat history, keeping "My conversations" focused on user-started chats while preserving automation outputs in their run details.
## Public alert automation
[Public alert definitions](/alerts-monitoring/create_alert) can opt into [AI investigations](/ai-sre/alert-investigations) when alerts fire, including alerts created through public API clients and external automation workflows.
## Faster Guardian execution
[Guardian](/ai-sre/overview) has a new execution runtime for chat and automated investigations. It improves benchmark results by 2x and makes long-running investigations more resilient when sessions reconnect or work resumes.
## Live automation progress
[Deployment verification](/ai-sre/deployment-verification), [alert investigations](/ai-sre/alert-investigations), [anomaly investigations](/ai-sre/anomaly-detection), service error investigations, issue-fixer automation, and repository auto-mapping now benefit from the same faster execution model. Active agent runs show live progress while work is running instead of waiting for final output.
## Public dashboard sharing
Admins can now share read-only dashboards outside their Metoro organization with [password-protected public access](/dashboards/public-access). Public viewers unlock a shared URL with a dashboard password and receive a short-lived dashboard token, while Metoro limits public data access to admin-approved query shapes.
## Query allowlists
[Public dashboard settings](/dashboards/public-access#public-queries) now extract widget queries for review, preserve approvals for unchanged queries, and mark new or changed queries as pending. Public metric, log, and trace endpoints reject requests that do not match an approved query shape.
## Viewer reliability
Public dashboard routes have been hardened so shared dashboards render with the same tooltip context as authenticated dashboards.
## Alert creation from charts
You can now [create alerts](/alerts-monitoring/create_alert) directly from [MetoroQL](/metrics/metoroql)-backed chart menus. The alert creation flow starts with the chart query prefilled, matching the existing workflow for standard metric charts.
## Chart display controls
[Chart Builder and Editor](/dashboards/creating-editing) now include first-class threshold controls. Add, edit, remove, label, and color threshold lines directly from Display Options without editing dashboard JSON.
## Dashboard workflow polish
[Dashboard charts](/dashboards/creating-editing) can be duplicated within their original group, chart loading states now show only a spinner until data is ready, and grouped dashboard headers have clearer expand/collapse controls.
## More actionable CPU throttling issues
[CPU throttling Advisor recommendations](/advisor/cpu-throttling) now identify the top contributing container when container-level metrics are available, including throttled seconds, CPU usage, and throttle ratio in the issue details drawer.
## SLO dashboard templates
[Dashboard templates](/dashboards/templates) now include service-level objective templates, giving teams a faster way to start tracking availability, latency, and error budget health in Metoro.
## More dashboard widgets
[Dashboards](/dashboards/widgets) now support more Grafana-style panel types natively:
* Table widgets for tabular metric data, with pagination, density, wrapping, column alignment, filtering, widths, precision, and unit controls.
* Bar Gauge widgets for comparing aggregate values as proportional bars.
* Pie and donut widgets for comparing aggregate metric values by category.
* Widget descriptions that appear as compact info tooltips and are preserved from imported Grafana panels.
## Better Grafana and Perses imports
Grafana imports now preserve more dashboard behavior when moving into Metoro. Imported dashboards keep dense 24-column layouts, static interval variables, hidden variables, table units, bar gauges, pie charts, descriptions, and more [MetoroQL](/metrics/metoroql) compatibility for PromQL-style expressions such as `round(...)`, `time()`, `clamp_min(...)`, scalar comparisons, and histogram quantiles.
## Authentication and setup
On-premises deployments can now use [generic OIDC login](/on-premises/10.x/installation/oidc), including group-to-role mapping for providers such as [Keycloak](/on-premises/10.x/installation/oidc-keycloak). Denied and expired OIDC login attempts now show clearer user-facing failure states, and the on-prem login page has been updated to match Metoro's dark product experience.
## Deeper Kubernetes visibility
[Kubernetes Resource Viewer](/kubernetes-resources/resource-viewer) added GPU visibility so infrastructure teams can inspect NVIDIA GPU usage alongside CPU, memory, and workload health.
## Better trace and investigation guidance
The [traces cheat sheet](/traces/cheat-sheet) gives new users a faster path through common trace-debugging questions, and trace views gained latency-focused sorting so slow requests are easier to find.
[Autonomous investigations](/ai-sre/anomaly-detection) can now detect pod failures, and alert setup includes a more guided onboarding path for teams adopting [alerting](/alerts-monitoring/alerts-overview).
## Refreshed Guardian workspaces
[Guardian](/ai-sre/overview) received a redesigned investigation experience across [issues](/ai-sre/issues), [alert investigations](/ai-sre/alert-investigations), and [anomaly investigations](/ai-sre/anomaly-detection). The new views make investigation status, findings, related resources, and next actions easier to scan.
## More transparent AI runs
AI SRE run views now show clearer live progress for long-running work, including validation runs and code-fix workflows connected through the [GitHub integration](/ai-sre/github-integration).
## Integration and administration updates
The [Metoro MCP Server](/integrations/metoro-mcp-server) docs were added for teams connecting Metoro context to AI tools, [billing settings](/administration/billing-overview) moved into the main settings area, and MetoroQL now shows clearer errors for invalid queries.
## Full-screen Guardian chat
[Assisted Debugging](/ai-sre/assisted-debugging) gained a full-screen Guardian experience with clearer plans, progress, conversation history, deep links, and memory across investigations.
## Repository-aware investigations
[GitHub-connected AI SRE workflows](/ai-sre/github-integration) can map services to repositories during onboarding, making code-aware debugging and issue-fix automation easier to start.
## Kubernetes resource exploration
[Kubernetes Resource Viewer](/kubernetes-resources/resource-viewer) expanded with historical resource queries and broader workload coverage. [Kubernetes events](/kubernetes-resources/kubernetes-events) also gained message filtering improvements and suggested filters for faster triage.
## AI usage visibility
[Billing settings](/administration/billing-overview) now show AI usage and quota information so admins can understand how Guardian usage maps to their account limits.
## Smarter deployment verification
[Deployment Verification](/ai-sre/deployment-verification) added an AI pre-check that can skip low-risk changes and explain why verification did or did not continue. Slack updates now include more context about the deployment, the decision, and the next step.
## More flexible AI providers
Guardian added support for additional enterprise AI provider configurations, giving enterprise teams more flexibility in how AI SRE requests are processed.
## Authentication polish
Login now handles organization selection more smoothly for users with a single available organization, reducing the number of steps needed to get back into Metoro.
## Deployment monitoring and verification
[Deployment Verification](/ai-sre/deployment-verification) became easier to adopt with onboarding updates, settings in the Features area, code-aware checks, repository annotations, and annotation-based controls for which deployments should be verified.
## Advisor and autonomous investigations
The issue experience was refreshed into [Advisor](/advisor/overview), and [autonomous investigations](/ai-sre/anomaly-detection) expanded to cover more production signals, including 5XX error anomalies.
## AI SRE controls and notifications
Guardian settings, AI usage terms, and notification behavior were updated so teams can manage AI SRE access more clearly. Event and inbox workflows also became available by default, with issue links included in more notifications.
## Events inbox and timelines
[AI SRE notifications](/ai-sre/notifications) expanded with an events inbox and richer timelines, giving teams a central place to review deployment activity, alert training events, and investigation updates.
## Alert and deployment workflows
Alerts can now trigger [Guardian investigations](/ai-sre/alert-investigations) when they fire, and deployment rollouts can start verification workflows for teams using [Deployment Verification](/ai-sre/deployment-verification).
## Onboarding and status page polish
New onboarding flows made it easier to get started with Metoro, while [status pages](/uptime-monitoring/status-pages), trace percentile units, chart filtering, and long-range time selection received user-facing cleanup.
## Folders and access control
[Dashboards](/dashboards/overview) and [alerts](/alerts-monitoring/alerts-overview) gained folder organization, including personal folders and role-aware access controls that help larger teams keep shared observability content organized.
## ConfigMap-managed dashboards
[ConfigMap-managed dashboards](/dashboards/configmap-managed) give Kubernetes teams a declarative way to manage dashboards alongside cluster configuration.
## AI runbooks and issues
[AI runbooks](/ai-sre/runbooks) and [AI SRE issues](/ai-sre/issues) became more integrated with day-to-day workflows, including creating alerts from issues and improving issue investigation views.
## Logs and trace query updates
[Log search](/logs/overview) restored regex search, and trace analytics gained more grouping support for duration percentile queries.
## Faster navigation and filtering
Metoro added broader service search, command-palette access to pods, and a more flexible filter panel so teams can move between services, workloads, and resources faster.
## User preferences and themes
Theme selection became easier with light and dark mode controls, and saved search fixes made [saved log searches](/logs/saved_searches) more reliable.
## Query fairness and operational polish
Workload scheduling improvements made shared query resources fairer across users. [Dashboards](/dashboards/overview), [alerts](/alerts-monitoring/alerts-overview), [uptime monitors](/uptime-monitoring/overview), and log attribute summaries also received reliability and performance polish.
## Modern authentication and access control
[Authentication](/user-management/authentication) expanded with SAML SSO, MFA, GitHub and Microsoft login, passkeys, and passwordless login options. [Role management](/user-management/rbac#roles) also gained SAML and Okta role-mapping improvements, including default SAML roles.
## API keys and incident integrations
Teams can now manage [API keys](/user-management/api-keys) more directly, and the [Rootly integration](/integrations/rootly) guide helps route Metoro alerts into incident workflows.
## Alert and log workflow improvements
Alert destinations now send clearer resolved notifications across Slack, email, and webhooks. [Saved searches](/logs/saved_searches) gained MetoroQL support with [custom columns](/logs/custom_columns), and log context views became easier to scan with sticky headings.
## Bring-your-own AI provider keys
Teams using AWS can configure [Bedrock for AI SRE](/ai-sre/aws-bedrock-setup), giving more control over how Guardian-backed workflows are powered.
## Autonomous anomaly investigations
[Anomaly Detection](/ai-sre/anomaly-detection) introduced autonomous AI investigations for unusual production behavior, with approval and feedback flows that help teams control how AI SRE acts.
## GitHub-connected remediation
The [GitHub integration](/ai-sre/github-integration) added support for issue creation, code-aware context, and fix workflows so teams can move from investigation to remediation without leaving Metoro.
## AI SRE issues and notifications
[AI SRE issues](/ai-sre/issues) gained export and environment filtering, while [AI SRE notifications](/ai-sre/notifications) and email templates made investigation updates easier to follow.
## Provider and log context updates
[AWS Bedrock setup](/ai-sre/aws-bedrock-setup) became available for teams bringing their own AI provider configuration, and log context improvements made investigation evidence easier to inspect.
## AI alert investigations
[Alert investigations](/ai-sre/alert-investigations) brought Guardian into alert response, helping teams understand why an alert fired and what evidence matters.
## Roles and billing visibility
[Role-based access control](/user-management/rbac) expanded user-management options, and [billing](/administration/billing-overview) gained usage, cost estimate, and node-minute visibility.
## Trace and log context
Trace views can show [related logs](/traces/common-questions#how-do-i-view-logs-for-a-specific-trace-or-span), and linked traces made it easier to move between related distributed traces during debugging.
## Better metric display
Metric charts gained richer unit support, including bytes, currency, and multi-unit displays. A new NVIDIA GPU dashboard template also gave GPU-heavy teams a faster starting point in [dashboard templates](/dashboards/templates).
## Log search, export, and transformations
[Logs](/logs/overview) gained [MetoroQL](/metrics/metoroql) support, [saved searches](/logs/saved_searches), [log export](/logs/logs_export), copiable log attributes, line wrapping, JSON severity parsing, and more responsive loading. [Log transformations](/logs/log_transformations) also became available for shaping attributes before they are used across logs, alerts, and side filters.
## Custom telemetry filtering
Trace and log ingestion gained custom attribute filtering, making it easier to drop noisy telemetry attributes before they clutter search, filters, dashboards, and investigations.
## Uptime and dashboard updates
[TCP uptime checks](/uptime-monitoring/tcp-port-monitoring) expanded endpoint monitoring beyond HTTP, and [status pages](/uptime-monitoring/status-pages) added refresh indicators. [Dashboard widgets](/dashboards/widgets) gained log and trace widgets, share controls, smoother variable handling, and more stable chart loading.
## Guardian with broader context
[Guardian](/ai-sre/assisted-debugging) became more capable at answering production debugging questions with logs, metrics, traces, Kubernetes resources, profiles, and source-code context from the [GitHub integration](/integrations/github).
## Distributed tracing improvements
[Trace views](/traces/overview) added span deep links, richer OpenTelemetry and eBPF guidance, related log context, multiple filter conditions, and better handling for services with sparse or missing span data.
## MetoroQL and declarative alerts
[MetoroQL](/metrics/metoroql) became available in more alert and dashboard workflows. [Alerts](/alerts-monitoring/create_alert) added ConfigMap-managed definitions, API-backed configuration, example alert docs, MetoroQL alerting, and templated alert titles and descriptions.
## Kubernetes events and service context
[Kubernetes events](/kubernetes-resources/kubernetes-events) became easier to visualize and correlate with logs, metrics, and traces, while service graph improvements made dependencies easier to inspect from service views.
## Guardian chat
[Guardian](/ai-sre/assisted-debugging) became a first-class debugging workspace with streaming responses, a dedicated page, log-to-Guardian actions, a keyboard shortcut, stop controls, and clearer progress while investigations run.
## Roles and user administration
[Role-based access control](/user-management/rbac) added managed roles, resource-scoped permissions, role-aware invitations, and a roles UI. [User management](/user-management/rbac#users) also gained clearer settings tabs and invitation flows.
## Service maps, filters, and charting
[Service map](/traces/service-map) was added to trace workflows, while logs, traces, and metric values gained regex filtering. Dashboard and metric charting also gained area lines, stat display options, histogram support, multi-metric aggregation, and better tooltip behavior.
## Operational evidence in logs
[Webhook](/integrations/webhooks) delivery results and uptime monitor results can be reported as log lines, giving teams searchable evidence for notification and endpoint-check behavior.
## Uptime monitoring and public status pages
[Uptime Monitoring](/uptime-monitoring/overview) added endpoint checks, uptime metrics, and docs for setting up monitors. [Public status pages](/uptime-monitoring/status-pages) made those checks easier to share with customers and stakeholders.
## Dashboard variables and Grafana imports
[Dashboard variables](/dashboards/variables) became available for reusable filters, including variables in titles and stat widgets. Grafana imports became more resilient, with clearer warnings when an imported dashboard needs manual review.
## Multi-metric alerts
[Alert configuration](/alerts-monitoring/alert_configuration) expanded to multi-metric alert creation, import and export flows, table views, clearer alert summaries, grouped alert details, and improved Slack notification formatting.
## Kubernetes JSONPath and trace redaction
[Kubernetes resource queries](/kubernetes-resources/kubernetes-resources#json-path-support) gained JSONPath filtering for resource manifests, and [trace redaction](/traces/redaction) docs were added for teams controlling sensitive trace attributes.
## Advisor issue detection
[Advisor](/advisor/overview) added early issue-detection workflows for production signals, including [OOM detection](/advisor/oom-detection) and [CPU throttling](/advisor/cpu-throttling). Issue lists, muting, and run details became easier to review.
## Dashboard templates and Kubernetes charts
[Dashboard templates](/dashboards/templates) gave teams predefined starting points for common monitoring views, while charting added multi-line support and Kubernetes-focused visualizations.
## Alert and homepage context
Alerts gained muting controls and richer attributes, and the home page added ingestion-rate visibility so teams could quickly see whether telemetry was arriving as expected.
## Dashboard variables and multi-metric charts
[Dashboard variables](/dashboards/variables) added reusable filters for dashboard groups, while [dashboard widgets](/dashboards/widgets) gained multiple metrics per chart, comparison options, default time ranges, and dashboard cloning.
## More flexible alert routing
[Alert destinations](/alerts-monitoring/alert_destinations) expanded to multiple destinations on the same alert, alert cloning, better recovery behavior, and clearer firing charts.
## Cluster and on-prem visibility
Service cards can link into Kubernetes views, cluster collector health surfaced more clearly, and on-premises installs gained UI support for viewing auth tokens and handling first-admin setup.
## Infrastructure view refresh
[Infrastructure View](/infrastructure/overview) received a major refresh with node-focused tables, utilization fixes, namespace filtering, pod drill-downs, and links from services into Kubernetes context.
## Dashboard usability
[Dashboards](/dashboards/overview) gained markdown note widgets, persistent URLs, default dashboard time periods, datapoint selection, and polish for chart alignment, query selectors, and metric catalogue behavior.
## Webhooks and account flows
[Webhook integrations](/integrations/webhooks) became available as alert destinations. Account setup also improved with invite-link UI, forgot-password handling, and default admin setup for on-premises installs.
## Kubernetes events
[Kubernetes events](/kubernetes-resources/kubernetes-events) were added as a durable, filterable event view so teams can inspect cluster changes, warning events, and service-associated events after Kubernetes would normally expire them.
## Metric explorer and catalogue updates
[Metrics](/metrics/overview) gained OpenTelemetry metric support, request and response size metrics, metric filters, an environment selector, host filtering, and a clearer split between metric explorer and catalogue workflows.
## Service map and trace performance
[Service map](/traces/service-map) added expandable service views, external service handling, protocol context, and availability-zone context, while trace queries became faster for large environments.
## AWS Marketplace and billing
[AWS Marketplace billing](/administration/billing-aws-marketplace) was added alongside Stripe billing improvements, usage reporting, node-hour accounting, account setup handling, and clearer billing-method switching.
## Always-on profiling
[Profiling](/profiling/overview) became available for service-level CPU investigation, including flamegraph views, container selection, and Python profiling support.
## Alert integrations
[PagerDuty](/integrations/pagerduty) and email alerting expanded alert routing options, while service graph and custom log attribute rendering improvements made alert context easier to inspect.
## Metric and trace alerting
[Alerts](/alerts-monitoring/create_alert) expanded beyond basic metric conditions with metric alerting fixes, trace alerting, trace rate alerts, and the ability to create alerts from metric views.
## Dashboard and metric exploration
[Dashboards](/dashboards/creating-editing) gained more flexible chart creation, including adding charts from more places, picker ranges in the metric selector, filterable legends, and clearer metric suggestions.
## Service graph and trace context
[Service map](/traces/service-map) gained external service context and request sorting, while traces added linked-span support, exported trace links, and better filtering across traces and metrics.
## Log exclusions and onboarding
[Log ingestion settings](/logs/ingestion-settings) gained richer exclusion filters, and install/onboarding flows added OpenTelemetry setup, multi-cluster settings, and PagerDuty connection steps.
## Faster trace and log filtering
[Trace](/traces/overview) and [log](/logs/overview) views gained better side filters, regex filters, selected-service log context, debounced filtering, and faster trace headers for large services.
## Kubernetes view performance
[Kubernetes resource views](/kubernetes-resources/kubernetes-resources) became faster and more stable, with cleaner pod lifecycle charts, current-running-service data, and better handling of large resource tables.
## Alert and ingestion reliability
Alert monitoring became significantly faster, and [ingestion settings](/logs/ingestion-settings) gained editable exclusion filters for teams controlling which telemetry enters Metoro.
## Dashboards and monitoring setup
[Dashboards](/dashboards/overview), dashboard creation, settings, monitoring creation, and [Slack channel selection](/integrations/slack) were added as core product workflows.
## Kubernetes infrastructure views
The first Kubernetes infrastructure experience added resource tables, YAML viewing, pod timelines, container state details, terminated-container handling, deep links, and safer resource export behavior that excludes secrets.
## Logs, traces, and structured logging
[Structured logging](/logs/structured-logs), log and trace ordering, log deep links, regex log alerts, loading states, and chart-based time selection made the initial observability workflows easier to use.
## User administration
[User management](/user-management/rbac#users) added invite links, pending-member handling, current-member views, and delete-user support so admins could manage access directly in Metoro.