Skip to content

Latest commit

 

History

History
67 lines (47 loc) · 4.09 KB

README.md

File metadata and controls

67 lines (47 loc) · 4.09 KB
Raw

ADX-Mon

ADX-Mon is a comprehensive observability platform that seamlessly integrates metrics, logs, traces, continuous profile and any telemetry into a unified platform. It addresses the traditional challenges of data being siloed and difficult to correlate, as well as the cardinality and scale issues found in existing metrics solutions, streamlining the collection and analysis of observability data.

Features

  • Unlimited Cardinality, Retention, and Granularity: No restrictions on data dimensions, storage duration, or detail level.
  • Low Latency Ingestion and Lightweight Collection: Ensures rapid data processing with minimal resource overhead.
  • Unified Alerting: Simplified alerting mechanisms for metrics, logs, and traces.
  • Powered by Azure Data Explorer (ADX): Built on the robust and scalable ADX platform with the powerful Kusto Query Language (KQL) unifying access to all telemetry.
  • Flexible and Standards-Based Interfaces: Supports OTEL, Prometheus, and other industry standards ingestion protocols.
  • Optimized for Kubernetes and Cloud-Native Environments: Designed to thrive in modern, dynamic infrastructures.
  • Pluggable Alerting Provider API: Customizable alerting integrations.
  • Broad Compatibility: Works seamlessly with Grafana, ADX Dashboards, PowerBI, and any ADX-compatible products.
  • Turnkey, Scalable, and Reliable: A ready-to-use observability platform that scales from hobby projects to enterprise-level deployments.

Learn More

Development

Contributing

This project is currently under heavy development and is changing frequently. We are currently only accepting contributions for bug fixes, test coverage and documentation. Feature requests will be considered after the project has reached a stable state.

Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

Testing alertrules

Prereq: some k8s cluster you have kubeconfig for (can be minikube or kind)

  1. az login to the account that has acces to the kusto clusters.
  2. apply crds : k apply -f kustomize/bases/alertrules_crd.yaml
  3. apply your alert rules (probably in a different repo)
  4. cd cmd/alerter
  5. go run . --kusto-endpoint "=" --kubeconfig ~/.kube/config. The database much match the one in your alert rule (case-sensitive)
  6. optionally specicfy arugments that will be filled into query if needed like --region uksouth
  7. You should both see "Creating query executor for..." and "Fake Alert Notification Recieved..." if your query gets results.