MicroCBR: Case-based Reasoning on Spatio-temporal Fault Knowledge Graph for Microservices Troubleshooting
- Online Boutique with OpenTelemetry
- Sock shop with OpenTelemetry
- Train ticket with OpenTelemetry
- Banks
- blackbox-exporter
- mongodb-exporter
- mysql-exporter
- rabbitmq-exporter
- redis-exporter
- jmx-exporter
- kube-state-metrics
- ping_exporter
- Chaos-mesh
- Manual injection
- k8s experiment
- Pod failure, kill, container kill
- Network disconnection, partition, high delays, high packet loss rate, packet reordering, limit bandwidth
- Stress of CPU, memory
- DNS error, wrong
- Time faults for clock skew
- JVM cpu-count stress, memory-type stress, trigger garbage collection
- HTTP patch
- physical nodes
- instance_related: whether the kb is peculiar to instance or not
- metrics: prometheus metrics, some of them rely on exporters
- index: index for queries from QUERY.yaml
- traces: Jaeger traces
- logs: k8s logs and application logs
- cmd: command line operations