Skip to main content

Release Notes

Current version: 1.5.9.

Upgrade method:

  • Docker Compose: update the image tag in x-ops-image at the top of ops.yaml, then run:

    docker compose -f ops.yaml pull
    docker compose -f ops.yaml up -d

  • Kubernetes: download the deployment manifests for the target version again and apply them over the existing resources.

Upgrade does not modify existing data volumes. Monitoring history and alert configuration are retained by default.

Read before upgrading from 1.4.x
  • Data source configuration: data sources are now maintained on the UI "Data Sources" page. ENV_MYSQL_*, ENV_REDIS_*, ENV_KAFKA_ENDPOINTS, ENV_ELASTICSEARCH_*, ENV_MONGODB_URI, ENV_PROMETHEUS_HOST, ENV_FLINK_URL, and similar variables in ops.yaml/ConfigMap are no longer read. Existing data sources are not affected, and these historical variables can be removed.
  • Object storage: logs and traces must use two different buckets, ENV_S3_BUCKET_LOKI and ENV_S3_BUCKET_TEMPO, and the buckets must be created before deployment.
  • Data directory: the /data/mdis/ layout applies only to new installations. Do not directly change existing data volume paths during upgrade.

v1.5 · July 2026​

This series consolidates collection configuration into a single entry point and improves Kubernetes monitoring, multi-cluster collection, and object storage capabilities.

Added​

  • YAML/JSON batch import and export for data sources, supporting batch onboarding, backup/restore, and cross-environment migration.
  • Connection tests now also check collection status, distinguishing reachable connections, active collection, and reachable connections with no data collected yet.
  • Kubernetes collection-component mode. Monitored clusters can push metrics back to the Ops Platform through remote_write, suitable for scenarios where the Ops Platform is outside the monitored cluster or manages multiple clusters.
  • Gateway endpoints with Bearer authentication for metric and log writes, used for multi-cluster metric reporting and cross-cluster log push.

Changed​

  • Data source configuration is unified on the UI "Data Sources" page. Historical data source variables in ops.yaml/ConfigMap no longer take effect.
  • Kubernetes monitoring now uses in-cluster collection: deploy the Ops Platform inside the monitored cluster, or install collection components in the monitored cluster.
  • Object storage for logs and traces is split into independent buckets. Component data directories are unified as /data/mdis/<component>.
  • Namespace, node label, and taint key are unified as hap-ops.

Key Fixes​

  • Fixed empty monitoring data after Kubernetes deployment, missing filter options on Kubernetes panels, and missing host monitoring data.
  • Fixed metric collection issues caused by MongoDB multi-node replica sets, credential passing, and insufficient permissions.
  • Fixed slow-query diagnostics hot reload, permission hints, and inaccurate exception classification.
  • Fixed inaccurate collection status display, invisible Flink connectivity state, and missing prefix in remote_write example addresses.
Patch version summary (1.5.0 - 1.5.9)
VersionHighlights
1.5.9Host panel fixes
Data source export
Connection test collection-status validation
1.5.8Kubernetes cluster identifier injection
Slow-query target hot reload
Flink connectivity status
1.5.7Kubernetes single-file manifest adds RBAC/kube-state-metrics
Bearer write endpoints
1.5.6Multi-node replica set MongoDB collection
1.5.5Kubernetes collection-component mode
MongoDB collection credential passing fix
1.5.4On-demand Docker log collection under Kubernetes
Cluster manifest download
1.5.3Kubernetes monitoring consolidated to in-cluster collection
1.5.2Data directory unified as /data/mdis/<component>
1.5.1Separate object storage buckets for logs and traces
1.5.0Unified data source entry point and batch import

v1.4 · July 2026​

This series introduces the alert subsystem and changes delivery to a single-image form.

Added​

  • Alert subsystem supporting rule types for basic resources, ports, SSL, MySQL, MongoDB, Kafka lag, Kafka rebalance, and more.
  • "Data Sources" page for centralized management of host, middleware, Kubernetes, and Flink data sources.
  • Collection status and deployment self-check capabilities, helping locate collection issues from the UI.
  • MongoDB slow-query analysis now supports sharded clusters and multi-instance aggregation.

Changed​

  • All components are merged into the ops-allinone image, with runtime roles distinguished by ROLE.
  • Alert rules, status, history, notification channels, and data source configuration are stored independently in ops-mongo.
  • Added required credential encryption key ENV_ALERT_CRYPTO_KEY.
  • Historical Grafana alert, notification, and silence configuration is replaced by the Ops Platform alert capability.

Key Fixes​

  • Fixed host monitoring loss after upgrade, incomplete default values when creating data sources through API, and duplicate data sources.
  • Fixed MySQL/MongoDB credential decryption, object storage compatibility, and ops-mongo startup order dependency issues.
  • Fixed tracing service-name matching that previously worked only for the default namespace.
Patch version summary (1.4.0 - 1.4.10)
VersionHighlights
1.4.10Host monitoring upgrade-loss fix
API data source defaults
Deployment self-check
1.4.8Data source collection status
1.4.6Tracing service names support any namespace
1.4.5ops-mongo background retry
Data sources enabled by default after creation
1.4.4Prometheus retention by size
1.4.3Object storage compatibility
Istio tracing appProtocol
1.4.1MySQL/MongoDB credential decryption
1.4.0Alert subsystem, unified data sources, and single-image delivery

v1.3 · June 2026​

  • Added Kubernetes cluster monitoring dashboards and menu.
  • Supported collecting multiple middleware instances with a single agent.
  • Loki supports retention policies and delete API.

v1.2 · April-May 2026​

  • Added log search and APM distributed tracing capabilities.
  • Split log panels into container console and service logs, with structured field expansion, full-text search, and multi-condition filtering.
  • Supported sub-path deployment.
  • Deployment resource requirements changed to 4C/8G.

v1.1 · February 2025​

  • Added MongoDB slow-query and index suggestion capabilities.

v1.0 · January 2025​

  • Initial version with system resource monitoring.