Skip to content

Glossary

Application resource group
Customer-controlled Azure resource group containing the Azure Managed Application resource.
Azure Managed Application
Azure Marketplace deployment model that creates an application resource together with a managed resource group containing the platform infrastructure.
Capacity profile
Initial platform sizing selection such as Small, Medium, or Large.
Certificate signing request (CSR)
Request generated by the managed platform and submitted to a certificate authority to obtain a TLS certificate. The platform retains the corresponding private key.
Data stream
Elasticsearch storage model commonly used for time-series data such as logs, metrics, and traces.
Deployment reference
Customer-facing identifier associated with a deployment and included in iVedha deployment notifications. Use it when requesting support or managed platform changes.
Elastic Agent
Elastic component used to collect telemetry, run integrations, and connect managed observability sources to Elasticsearch.
Elastic connectors
Elastic services that integrate supported external content sources or services with Elasticsearch workflows.
Elasticsearch
Distributed search, analytics, and data platform used for indexing, search, observability data, and vector or semantic-search workloads.
Fleet
Kibana-based management interface used to centrally manage Elastic Agents, agent policies, integrations, enrollment, and health.
Fleet Server
Service that coordinates communication between Fleet and enrolled Elastic Agents.
Ingestion
Process of sending data into Elasticsearch.
Kibana
Elastic browser interface for search, dashboards, observability, Fleet, security administration, and other supported Elastic features.
Logstash
Elastic data-processing service used for specialized ingestion, transformation, enrichment, and routing pipelines.
Managed resource group
Azure resource group containing the infrastructure operated as part of the Managed Application. Customers should not modify managed resources directly unless explicitly documented.
OpenTelemetry (OTel)
Open observability standard and ecosystem for producing and transmitting logs, metrics, and traces using common APIs, protocols, and semantic conventions.
OpenTelemetry Collector
Runtime component that receives, processes, enriches, and routes OpenTelemetry logs, metrics, and traces.
OTLP
OpenTelemetry Protocol used to transport telemetry between applications, collectors, agents, and observability backends.
Private DNS
DNS configuration that resolves service hostnames to private addresses for approved private networks.
Private Endpoint
Customer-owned Azure network interface that provides private connectivity to a supported service through a private IP address in a VNet.
Private Link
Azure private-connectivity technology used to access services without exposing the connection over the public internet.
Private Link Service
Service-side Azure resource to which a customer-created Private Endpoint connects. Use the deployment-provided resource information rather than reconstructing its resource ID.
Public access
Deployment configuration in which supported platform endpoints can be reached through public network paths, subject to TLS, authentication, and customer security controls.
Search workload
Platform use case focused primarily on indexing and querying application, document, knowledge, vector, or other search data.
Observability workload
Platform use case focused primarily on logs, metrics, traces, and operational analytics.
Semantic conventions
OpenTelemetry conventions that standardize the names and meaning of telemetry attributes and signals.
Snapshot
Elasticsearch backup stored in a configured snapshot repository and used for supported recovery workflows.
Subject Alternative Name (SAN)
Certificate field that identifies the hostnames for which a TLS certificate is valid.

The platform-generated CSR includes the required SANs for enabled deployment services such as Elasticsearch, Kibana, Fleet, and Logstash.

TLS
Transport Layer Security protocol used to encrypt connections and verify service identity using certificates.
Topology
Elasticsearch deployment layout describing how node roles and data tiers are organized.
Your deployment is ready
iVedha notification indicating that managed-platform readiness checks have completed successfully. This is the customer-facing readiness signal for starting post-deployment configuration.

Return to documentation

Return to the documentation home to choose a planning, deployment, operations, support, or reference task.