Arista LANZ and Loki Integration

Input and output integration overview

The Arista LANZ plugin is designed for reading latency and congestion metrics from Arista LANZ, helping users monitor their network performance effectively.

The Loki plugin allows users to send logs to Loki for aggregation and querying, leveraging Loki’s efficient storage capabilities.

Integration details

Arista LANZ

This plugin provides a consumer for use with Arista Networks’ Latency Analyzer (LANZ). Metrics are read from a stream of data via TCP through port 50001 on the switches management IP. The data is in Protobuffers format, allowing for efficient transportation and parsing of data. LANZ is utilized to monitor network latency and congestion in real-time, which is vital for maintaining optimal performance in networking environments. The underlying technology, Arista’s latency analysis, provides insights into various network operations and infrastructure behaviors, making it a crucial tool for network engineering and management.

Loki

This Loki plugin integrates with Grafana Loki, a powerful log aggregation system. By sending logs in a format compatible with Loki, this plugin allows for efficient storage and querying of logs. Each log entry is structured in a key-value format where keys represent the field names and values represent the corresponding log information. The sorting of logs by timestamp ensures that the log streams maintain chronological order when queried through Loki. This plugin’s support for secrets makes it easier to manage authentication parameters securely, while options for HTTP headers, gzip encoding, and TLS configuration enhance the adaptability and security of log transmission, fitting various deployment needs.

Configuration

Arista LANZ

[[inputs.lanz]]
  ## URL to Arista LANZ endpoint
  servers = [
    "tcp://switch1.int.example.com:50001",
    "tcp://switch2.int.example.com:50001",
  ]

Loki

[[outputs.loki]]
  ## The domain of Loki
  domain = "https://loki.domain.tld"

  ## Endpoint to write api
  # endpoint = "/loki/api/v1/push"

  ## Connection timeout, defaults to "5s" if not set.
  # timeout = "5s"

  ## Basic auth credential
  # username = "loki"
  # password = "pass"

  ## Additional HTTP headers
  # http_headers = {"X-Scope-OrgID" = "1"}

  ## If the request must be gzip encoded
  # gzip_request = false

  ## Optional TLS Config
  # tls_ca = "/etc/telegraf/ca.pem"
  # tls_cert = "/etc/telegraf/cert.pem"
  # tls_key = "/etc/telegraf/key.pem"

  ## Sanitize Tag Names
  ## If true, all tag names will have invalid characters replaced with
  ## underscores that do not match the regex: ^[a-zA-Z_:][a-zA-Z0-9_:]*.
  # sanitize_label_names = false

  ## Metric Name Label
  ## Label to use for the metric name to when sending metrics. If set to an
  ## empty string, this will not add the label. This is NOT suggested as there
  ## is no way to differentiate between multiple metrics.
  # metric_name_label = "__name"

Input and output integration examples

Arista LANZ

1. Real-Time Latency Monitoring: This plugin can be used to set up a monitoring dashboard that tracks real-time latency metrics across multiple interfaces. By gathering and visualizing this data, network admins can swiftly identify and rectify latency issues before they impact service quality. The challenge lies in efficiently handling the influx of metrics from various sources without overwhelming the infrastructure or incurring excessive processing delays.

2. Congestion Analysis for Traffic Engineering: Users can leverage the LANZ plugin to analyze congestion records, enabling the optimization of network traffic flows. By applying historical pattern recognition to the metrics collected, IT teams can make informed decisions on traffic management strategies, thus improving overall network efficiency. This requires implementing robust data storage and analysis capabilities to derive actionable insights from the raw metrics.

3. Integration with Alerting Systems: Integrate the metrics from this plugin with alerting systems to automatically notify network engineers of any significant changes in latency or congestion. By setting thresholds based on historical data trends, this use case enhances proactive incident management, allowing teams to address potential issues proactively. The technical challenge here is establishing the right balance in threshold settings to minimize false positives while ensuring genuine issues are flagged promptly.

4. Network Optimization Reports: Utilize the metrics gathered through the LANZ plugin to generate periodic reports that detail network performance, latency trends, and congestion events. These reports can help stakeholders understand network health over time and guide infrastructure investments. The challenge involves structuring and formatting the output data to make it comprehensible and actionable for various audiences.

Loki

1. Centralized Logging for Microservices: Utilize the Loki plugin to gather logs from multiple microservices running in a Kubernetes cluster. By directing logs to a centralized Loki instance, developers can monitor, search, and analyze logs from all services in one place, facilitating easier troubleshooting and performance monitoring. This setup streamlines operations and supports rapid response to issues across distributed applications.

2. Real-Time Log Anomaly Detection: Combine Loki with monitoring tools to analyze log outputs in real-time for unusual patterns that could indicate system errors or security threats. Implementing anomaly detection on log streams enables teams to proactively identify and respond to incidents, thereby improving system reliability and enhancing security postures.

3. Enhanced Log Processing with Gzip Compression: Configure the Loki plugin to utilize gzip compression for log transmission. This approach can reduce bandwidth usage and improve transmission speeds, especially beneficial in environments where network bandwidth may be a constraint. It’s particularly useful for high-volume logging applications where every byte counts and performance is critical.

4. Multi-Tenancy Support with Custom Headers: Leverage the ability to add custom HTTP headers to segregate logs from different tenants in a multi-tenant application environment. By using the Loki plugin to send different headers for each tenant, operators can ensure proper log management and compliance with data isolation requirements, making it a versatile solution for SaaS applications.

Feedback

Thank you for being part of our community! If you have any general feedback or found any bugs on these pages, we welcome and encourage your input. Please submit your feedback in the InfluxDB community Slack.