WIP: support log event stream processing and format improvement

[haf]

• remove pollServices in registry

  Because supervisor will supervise minions, if an exception occurs, it will be handled according to policy. So there's no need for state polling, because we can't do much if we can get the status. the user's handle logic can be expressed by policy.

• remove healthcheck & metric

  The aim here is to normalise the Gauge/Derived/Message semantics into a single semantic of 'things computed from events from your app'.

  • remove healthcheck

    Looks like metric can also be seen as a healthcheck, such as windows performance counters. when outside tick , metric generate some msg, which will be processed by user defined engine , they can decide their meaning (log or metric or healthcheck...) there.

  • remove metric

    metric can be implemented by engine's process expression builder, what we need to do is schedule jobs for tick, in the corresponding time(like old metricConf.tickInterval) or manually tick. Metric's data sources can have two types, one is similar to WPC, generate data in real-time when ticked .the other is generate through the normal log message.

• support multi targets on internallogger and apply rules when send msg to target

• redefined Message

  The aim here is to normalise the Gauge/Derived/Message semantics into a single semantic of 'things computed from events from your app'.

  • remove FieldModule.fs
  • use FsMessageTemplate for default MessageWriter
  • remove Chiron json support for message type
  • no need SuppressPointValue
  • use obj instead of Value Modle
  • gauges are stored in contexts with gauge type. so message.value is template or raw message.

• errors (exceptions)

  is expressed by a context, not a field. user can define their own output template for decision whether or not to show them.

• formatting

  contexts other than fields in template will destructure with @ in default message writer

• todo

  • more unit test

    • message
    • ewma & percentile
    • formatting
      • migrate old formatting tests
      • consider msg with gauges
      • consider msg with gauges, fields, contexts
    • migrate old core targets tests
    • registry

  • migrate whole solution help wanted

    • facade
    • targets
    • SuaveReporter
    • Targets.InfluxDb
    • examples with new style

  • event format improvement mentioned by event format proposal #257

  • reorganize types in Events.fs

  • Support building for .Net Core and .Net FW

  • to be discussed

    • do we need both logWithAck and log api in Logger type,beacuse log is just delegate call on logWithAck and ignore its result (promise)
    • registry/logmanager IDisposable ?
    • csharp factory support processing
    • new healthcheck/metric style

[haf]

Now, let's see what SuaveReporter can be fidxed with

[haf]

Should be fairly stable to build now; yet to run all tests and fix suave reporter and influx, but I did set up a docker compose that runs influxdb locally on docker, so the distance to go there should be pretty small.

[haf]

Builds on CI now, failing on tests due to ordering errors of new TypeShape file.

[lust4life]

@haf nice, glad you come back to push forward. will follow up in later days,a little busy these two days .

[haf]

What do you think of this?

We need some mechanism for ignoring certain properties from the JSON input, too.