Elastic.CommonSchema 1.4.0-beta1

Prefix Reserved
This is a prerelease version of Elastic.CommonSchema.
There is a newer version of this package available.
See the version list below for details.
dotnet add package Elastic.CommonSchema --version 1.4.0-beta1                
NuGet\Install-Package Elastic.CommonSchema -Version 1.4.0-beta1                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="Elastic.CommonSchema" Version="1.4.0-beta1" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Elastic.CommonSchema --version 1.4.0-beta1                
#r "nuget: Elastic.CommonSchema, 1.4.0-beta1"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install Elastic.CommonSchema as a Cake Addin
#addin nuget:?package=Elastic.CommonSchema&version=1.4.0-beta1&prerelease

// Install Elastic.CommonSchema as a Cake Tool
#tool nuget:?package=Elastic.CommonSchema&version=1.4.0-beta1&prerelease                

Elastic Common Schema .NET

Introduction

The Elastic.CommonSchema project contains a full C# representation of the Elastic Common Schema (ECS) YAML schema - see documentation.

The intention is that this library forms a reliable and correct basis for integrations into Elasticsearch, that use both Microsoft .NET and the ECS schema.

These types can be used in either as-is, or in conjunction with, the Elasticsearch.net client libraries. The types are annotated with the corresponding DataMember attributes, enabling out-of-the-box serialisation support with the Elasticsearch.net clients.

Packages

The .NET assemblies are published to nuget under the package name Elastic.CommonSchema

The master branch pushes new nuget packages on successful CI builds to https://ci.appveyor.com/nuget/ecs-dotnet

Versioning

The version of the package matches the published ECS schema version, with the same corresponding branch names.

  • Nested Schema (C# types generated from this resource): https://github.com/elastic/ecs/blob/v{version}/generated/ecs/ecs_nested.yml
  • .NET types: https://github.com/elastic/ecs-dotnet/tree/{version}

Where {version} is the ECS schema version, e.g. 1.2.0.

Further Compatibility Clarifications

The version numbers of the nuget package must match the exact version of the ECS schema used within Elasticsearch.

Attempting to use mismatched versions, for example; a nuget package with version 1.2.0 against an Elasticsearch index configured to use an ECS template with version 1.1.0 will result in indexing and data problems.

Getting started

Installing

You can install Elastic.CommonSchema from the package manager console:

PM> Install-Package Elastic.CommonSchema

Alternatively, simply search for Elastic.CommonSchema in the package manager UI.

Usage

Client Installation

In this example, we will also install the Elasticsearch.net Low Level Client and use this to perform the HTTP communications with our Elasticsearch server.

PM> Install-Package Elasticsearch.Net
Connecting to Elasticsearch
var node = new Uri("http://localhost:9200");
var config = new ConnectionConfiguration(node);
var lowLevelClient = new ElasticLowLevelClient(config);
Creating an Index Template

Now we need to put an index template, so that any new indices that match our configured index name pattern are to use the ECS schema.

We ship with different index templates for different major versions of Elasticsearch within the Elastic.CommonSchema.Elasticsearch namespace.

// We are using Elasticsearch version 7.4.0, lets use a 7 version index template
var template = Elastic.CommonSchema.Elasticsearch.IndexTemplates.GetIndexTemplateForElasticsearch7("ecs-*");

// Send the template to the Elasticsearch server
var templateResponse = lowLevelClient.Indices.PutTemplateForAll<StringResponse>("ecs-template", template);
   
// Check everything was successful
Debug.Assert(templateResponse.Success);

Now that we have applied the index template, any indices that match the pattern ecs-* will use the ECS schema.

NOTE: We only need to apply the index template once.

Creating an ECS event

Creating a new ECS event is as simple as newing up an instance:

var ecsEvent = new Base
{
    Timestamp = DateTimeOffset.Parse("2019-10-23T19:44:38.485Z"),
    Dns = new Dns
    {
        Id = "23666",
        OpCode = "QUERY",
        Type = "answer",
        Question = new DnsQuestion
        {
             Name   = "www.example.com",
             Type = "A",
             Class = "IN",
             RegisteredDomain = "example.com"
        },
        HeaderFlags = new [] { "RD", "RA" },
        ResponseCode = "NOERROR",
        ResolvedIp = new [] { "10.0.190.47", "10.0.190.117" },
        Answers = new []
        {
            new DnsAnswers
            {
                Data = "10.0.190.47",
                Name = "www.example.com",
                Type = "A",
                Class = "IN",
                Ttl = 59
            },
            new DnsAnswers
            {
                Data = "10.0.190.117",
                Name = "www.example.com",
                Type = "A",
                Class = "IN",
                Ttl = 59
            }
        }
    },
    Network = new Network
    {
        Type = "ipv4",
        Transport = "udp",
        Protocol = "dns",
        Direction = "outbound",
        CommunityId = "1:19beef+RWVW9+BEEF/Q45VFU+2Y=",
        Bytes = 126
    },
    Source = new Source
    {
        Ip = "192.168.86.26",
        Port = 5785,
        Bytes = 31
    },
    Destination = new Destination
    {
        Ip = "8.8.4.4",
        Port = 53,
        Bytes = 95
    },
    Client = new Client
    {
        Ip = "192.168.86.26",
        Port = 5785,
        Bytes = 31
    },
    Server = new Server
    {
        Ip = "8.8.4.4",
        Port = 53,
        Bytes = 95
    },
    Event = new Event
    {
        Duration = 122433000,
        Start = DateTimeOffset.Parse("2019-10-23T19:44:38.485Z"),
        End = DateTimeOffset.Parse("2019-10-23T19:44:38.607Z"),
        Kind = "event",
        Category = "network_traffic"
    },
    Ecs = new Ecs
    {
        Version = "1.2.0"
    },
    Metadata = new Dictionary<string, object>
    {
        { "client", "ecs-dotnet" }
    }
};

This can then be indexed into Elasticsearch:

var indexResponse = lowLevelClient.Index<StringResponse>(index,PostData.Serializable(ecsEvent));

// Check everything was successful
Debug.Assert(indexResponse.Success);

Congratulations, you are now using the Elastic Common Schema!

A note on the Metadata property

The C# Base type includes a property called Metadata with the signature:

/// <summary>
/// Container for additional metadata against this event.
/// </summary>
[DataMember(Name = "_metadata")]
public IDictionary<string, object> Metadata { get; set; }

This property is not part of the ECS specification, but is included as a means to index supplementary information.

This software is Copyright (c) 2014-2020 by Elasticsearch BV.

This is free software, licensed under: The Apache License Version 2.0.

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 is compatible. 
.NET Framework net461 is compatible.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (12)

Showing the top 5 NuGet packages that depend on Elastic.CommonSchema:

Package Downloads
Elastic.CommonSchema.Serilog

Serilog TextFormatter that formats log events in accordance with Elastic Common Schema (ECS).

Elastic.Ingest.Elasticsearch.CommonSchema

Package Description

Elastic.CommonSchema.NLog

NLog Layout that formats log events in accordance with Elastic Common Schema (ECS).

Elastic.Extensions.Logging

Elasticsearch logger provider for Microsoft.Extensions.Logging. Writes direct to Elasticsearch using the Elastic Common Schema (ECS), with semantic logging of structured data from message and scope values, for use with the Elasticsearch-Logstash-Kibana (ELK) stack. The results can be viewed and queried in the Kibana console.

Elasticsearch.Extensions.Logging

Elasticsearch logger provider for Microsoft.Extensions.Logging. Writes direct to Elasticsearch using the Elastic Common Schema (ECS), with semantic logging of structured data from message and scope values, for use with the Elasticsearch-Logstash-Kibana (ELK) stack. The results can be viewed and queried in the Kibana console.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
8.12.2 84,393 10/22/2024
8.12.1 140,803 10/3/2024
8.12.0 31,985 9/26/2024
8.11.1 750,287 6/10/2024
8.11.0 563,787 4/10/2024
8.6.1 2,053,601 8/3/2023
8.6.0 461,546 5/9/2023
8.4.0-alpha4 36,123 3/28/2023
8.4.0-alpha3 13,940 3/15/2023
8.4.0-alpha2 2,085 3/1/2023
8.4.0-alpha1 2,381 2/20/2023
1.6.0-alpha1 276,415 6/2/2021
1.5.3 8,148,736 6/1/2021
1.5.1 1,594,361 6/3/2020
1.5.0 381,900 3/30/2020
1.4.4 3,556 3/25/2020
1.4.3 7,147 3/16/2020
1.4.2 26,300 3/6/2020
1.4.1 12,083 2/26/2020
1.4.0 15,035 1/29/2020
1.4.0-beta1 829 1/7/2020
1.2.0-alpha1 989 11/15/2019