Verwaltung von Zeitreihendaten
Optimieren Sie Elasticsearch für Zeitreihendaten, einschließlich Data Streams, ILM (Index Lifecycle Management) und Hot-Warm-Cold-Architekturen.
Verwaltung von Zeitreihendaten ist eine kostenlose Elasticsearch & Full Text Search Systems-Lektion auf CoddyKit. Dies ist Lektion 2 von 4. Du kannst die komplette Lektion unten kostenlos lesen – dann übst du sie direkt im Browser mit einem integrierten Code-Editor und einem KI-Tutor rund um die Uhr. Sie ist Teil des Elasticsearch & Full Text Search Systems-Lernpfads, und dein Fortschritt wird über Web und CoddyKit-App synchronisiert. Der Elasticsearch & Full Text Search Systems-Kurs umfasst insgesamt 4 Lektionen.
Teile dieser Lektion wurden noch nicht übersetzt und werden auf Englisch angezeigt.
What is Time-Series Data?
Time-series data is information collected over a period of time, often at regular intervals. Think of it as a sequence of data points indexed by time.
Examples include:
- System logs: Events happening on a server.
- IoT sensor readings: Temperature, humidity from devices.
- Financial data: Stock prices over days or hours.
This data is typically append-only and usually immutable once recorded.
Why Elasticsearch for Time-Series?
Elasticsearch is an excellent choice for managing time-series data due to its:
- Scalability: Handles massive volumes of data.
- Speed: Fast indexing and search capabilities.
- Analytics: Powerful aggregations for insights.
- Flexibility: Can store structured and unstructured data.
It's particularly strong for use cases like log analytics, metric monitoring, and security event management.
Introducing Data Streams
Data streams are a core feature in Elasticsearch designed specifically for time-series data. They simplify management by automatically rolling over to new indices as needed.
When you index data into a data stream, it always writes to the current write index. Queries, however, search across all backing indices transparently. This makes managing large, continuously growing datasets much easier.
Creating Your First Data Stream
To create a data stream, you first need an index template that defines its structure and points to a data stream.
Then, simply indexing a document into the stream's name will create it automatically based on the template:
PUT _index_template/my-data-stream-template
{
"index_patterns": ["my-data-stream-*"],
"data_stream": {},
"priority": 200,
"template": {
"settings": {
"number_of_shards": 1
},
"mappings": {
"properties": {
"@timestamp": {
"type": "date",
"format": "strict_date_optional_time||epoch_millis"
},
"message": { "type": "text" }
}
}
}
}
// Indexing a document creates the stream
POST my-data-stream/_doc
{
"@timestamp": "2023-10-27T10:00:00Z",
"message": "Sensor reading: 25.5C"
}Automating with ILM
Index Lifecycle Management (ILM) is a powerful feature that automates the management of your indices through various phases of their life.
For time-series data, ILM helps you:
- Automatically roll over indices when they reach a certain size or age.
- Move older, less frequently accessed data to cheaper storage.
- Delete data that is no longer needed.
The Four ILM Phases
ILM policies define actions for indices across four main phases:
- Hot: Indices are actively being written to and frequently queried. Requires fast storage.
- Warm: Indices are no longer being written to, but are still queried. Can be read-only and potentially on slower storage.
- Cold: Indices are rarely queried and often stored on very cheap, slow storage.
- Delete: Indices are no longer needed and are safely removed from the cluster.
Crafting an ILM Policy
Here's an example of an ILM policy that defines rollover, forcemerge (for warm phase), and deletion stages for time-series data:
PUT _ilm/policy/my-ts-policy
{
"policy": {
"phases": {
"hot": {
"actions": {
"rollover": {
"max_age": "7d",
"max_docs": 10000000,
"max_size": "50gb"
}
}
},
"warm": {
"min_age": "30d",
"actions": {
"forcemerge": {
"max_num_segments": 1
},
"shrink": {
"number_of_shards": 1
}
}
},
"cold": {
"min_age": "90d",
"actions": {
"freeze": {}
}
},
"delete": {
"min_age": "180d",
"actions": {
"delete": {}
}
}
}
}
}Hot-Warm-Cold Architecture
A Hot-Warm-Cold architecture optimizes resource utilization and cost for time-series data by using different types of nodes for different ILM phases.
- Hot nodes: Use fast CPUs, SSDs for high indexing and query throughput.
- Warm nodes: Use less powerful CPUs, HDDs (or slower SSDs) for older, read-only data.
- Cold nodes: Use very cheap, high-capacity storage, potentially even object storage, for rarely accessed data.
Assigning Node Roles
You can configure nodes to serve specific roles (hot, warm, cold) by setting node.attr in their elasticsearch.yml configuration file.
ILM policies then use these attributes to automatically move indices to the appropriate node types as they transition through phases.
# For a hot node
node.roles: [ data ]
node.attr.data: hot
# For a warm node
node.roles: [ data ]
node.attr.data: warm
# For a cold node
node.roles: [ data ]
node.attr.data: coldILM & Data Stream Check
Which of the following statements about Elasticsearch's time-series features are TRUE?
Time-Series Recap
Great job! You've explored how Elasticsearch is optimized for time-series data.
We covered:
- Data Streams: Simplifying index management and rollovers.
- ILM (Index Lifecycle Management): Automating index transitions through hot, warm, cold, and delete phases.
- Hot-Warm-Cold Architectures: Optimizing cluster resources and costs by assigning different node types to specific ILM phases.
These features are essential for building scalable and cost-effective time-series solutions with Elasticsearch.
Häufig gestellte Fragen
Ist die Lektion „Verwaltung von Zeitreihendaten“ kostenlos?
Ja — der vollständige Text von „Verwaltung von Zeitreihendaten“ ist hier im Web kostenlos zu lesen. Um sie interaktiv zu üben (integrierter Code-Editor und 24/7 KI-Tutor) und den Rest des Elasticsearch & Full Text Search Systems-Kurses freizuschalten, upgrade auf CoddyKit PRO. Der Elasticsearch & Full Text Search Systems-Kurs umfasst insgesamt 4 Lektionen.
Was lerne ich in „Verwaltung von Zeitreihendaten“?
Optimieren Sie Elasticsearch für Zeitreihendaten, einschließlich Data Streams, ILM (Index Lifecycle Management) und Hot-Warm-Cold-Architekturen. Du übst Elasticsearch & Full Text Search Systems mit praktischem Code, den du direkt im Browser ausführst, und ein 24/7 KI-Tutor beantwortet deine Fragen während du die Lektion bearbeitest.
Brauche ich Erfahrung, um Elasticsearch & Full Text Search Systems zu starten?
Keine Vorkenntnisse erforderlich. Elasticsearch & Full Text Search Systems auf CoddyKit ist für Anfänger bis fortgeschrittene Lernende strukturiert, sodass du hier starten oder von Anfang an beginnen und in deinem eigenen Tempo voranschreiten kannst. Dies ist Lektion 2 von 4.
Wie lange dauert die Lektion „Verwaltung von Zeitreihendaten“?
Die meisten CoddyKit-Lektionen dauern etwa 5–10 Minuten. Jede ist kompakt und interaktiv, sodass du stetig Fortschritte machst und genau dort weitermachst, wo du aufgehört hast – im Web und in der App.
Kann ich in dieser Elasticsearch & Full Text Search Systems-Lektion Code schreiben und ausführen?
Ja. Jede Elasticsearch & Full Text Search Systems-Lektion enthält einen integrierten Code-Editor, sodass du echten Code direkt in deinem Browser schreibst und ausführst und sofort KI-Feedback erhältst — ohne lokale Einrichtung erforderlich.
Alle Lektionen in diesem Kurs
- Geospatiale Suchfunktionen
- Verwaltung von Zeitreihendaten
- Strategien für den Produktivbetrieb
- Index-Lifecycle-Management