Please enable JavaScript.

Coggle requires JavaScript to display documents.

Technical practcies of feedback (Create Telemetry to Enable Seeing and…

- - - - Event router
        
        enables visualization, trending, alerting, anomaly detection, etc.
        
        collecting, storing, aggregating and transforming the telemetry
        
        perform statistical ops on metrics
      - Data collection at the business logic, application, and environments layer
        
        Logs, events, metrics
        
        Logs sent to a common service that enables easy centralization, rotation, and deletion
      - Sources
        
        Production
        
        Deployment pipeline
        
        Pre-production
      - Create self-service access to telemetry and information radiators
        
        Telemetry must be fast, easy to get, and sufficiently centralized, everyone in the value stream can share a common view of reality
        
        Self-service APIs
        
        Telemetry displayed in very visible places
      - Standardization of technological choices
    - - Infrastructure
      - Deployment pipeline (see below)
      - Application
        
        Front end / Client software
        
        Back end
      - Business
        
        Actionable metrics vs vanity metrics
        Detect if we are achieving our business goals
  - - - Set logging levels and criteria per level:
        Debug
        Info
        Warn
        Error
        Fatal
      - Requirements per telemetry consumers
        
        Ops
        
        Infosec
        
        Developers
        
        Business/prod management
      - List events to monitor
        Authentication/authorization decisions (including logoff)
        System and data access
        System and application changes (especially privileged changes)
        Data changes, such as adding, editing, or deleting data
        Invalid input (possible malicious injection, threats, etc.)
        Resources (RAM, disk, CPU, bandwidth, or any other resource that has hard or soft limits)
        Health and availability
        Startups and shutdowns
        Faults and errors
        Circuit breaker trips
        Delays
        Backup success/failure
        etc.
      - Define logging hierarchies to process and digest events and logs
        
        Non-functional
        
        e.g., performance, security
        
        For attributes related to features (e.g., search, ranking)
      - Tooling
        
        Create entries
        StatsD, Dynatrace, collectd,
        Plot
        Graphite, grafana
  - - - an automated communications process by which measurements and other data are collected at remote points and are subsequently transmitted to receiving equipment for monitoring
- - - - involves using moving averages (or rolling averages), which transform our data by averaging each point with all the other data within our sliding window. This has the effect of smoothing out short-term fluctuations and highlighting longer-term trends or cycles