[O11y][System] Rally benchmark system.memory#9296
Conversation
🚀 Benchmarks reportTo see the full report comment with |
|
@aliabbas-elastic Please add sample_event.json. |
Done. Please have a look |
| min: 8000000000 | ||
| max: 9000000000 |
There was a problem hiding this comment.
How these ranges contribute to the benchmark? If I tune these parameters, will the result change?
There was a problem hiding this comment.
These ranges just provide you the liberty to set fields with realistic values. Like for example here the values are correlated with each other. If you see the system_memory_actual_used_bytes ranges compared to this they would be lesser which will be the case in real environments as well. Modifying these wouldn't change the benchmarking stats.
| @@ -0,0 +1,35 @@ | |||
| fields: | |||
| - name: timestamp | |||
| period: -60m | |||
There was a problem hiding this comment.
This is in reference to this doc
https://github.com/elastic/elastic-integration-corpus-generator-tool/blob/main/docs/fields-configuration.md#:~:text=generator%20will%20stop.-,period,-optional%20(date
It would always generate documents before time.Now() so that the events would always be available in Last duration in Discover
… into system_benchmark_memory
💚 Build Succeeded
History
cc @aliabbas-elastic |
|



Proposed commit message
memorydata stream ofSystemSample Response
sample_event.json
{ "@timestamp": "2024-03-12T09:03:56.592Z", "agent": { "ephemeral_id": "22ed892c-43bd-408a-9121-65e2f5b6a56e", "id": "de42127b-4db8-4471-824e-a7b14f478663", "name": "system-scale-123456", "type": "metricbeat", "version": "8.8.0" }, "benchmark_metadata": { "info": { "benchmark": "memory-benchmark", "run_id": "4fcdf3ec-7f80-4ec2-9e5f-bc6515e5caf9" } }, "data_stream": { "dataset": "system.memory", "namespace": "ep", "type": "metrics" }, "ecs": { "version": "8.0.0" }, "elastic_agent": { "id": "404fc805-04b8-420a-9fcf-12d54b89d4fd", "snapshot": false, "version": "8.12.1" }, "event": { "agent_id_status": "auth_metadata_missing", "dataset": "system.memory", "duration": 64088, "ingested": "2024-03-12T09:04:01Z", "module": "system" }, "host": { "architecture": "x86_64", "containerized": true, "hostname": "docker-fleet-agent", "id": "96bd755dd266474fb86bd80a98cbaad5", "ip": "192.168.241.7", "mac": "02-42-C0-A8-F1-07", "name": "docker-fleet-agent", "os": { "codename": "focal", "family": "debian", "kernel": "3.10.0-1160.105.1.el7.x86_64", "name": "Ubuntu", "platform": "ubuntu", "type": "linux", "version": "20.04.6 LTS (Focal Fossa)" } }, "metricset": { "name": "memory", "period": 10000 }, "service": { "type": "system" }, "system": { "memory": { "actual": { "free": 4010742085, "used": { "bytes": 6897315189, "pct": 0.632 } }, "cached": 1193489350, "free": 2942436459, "swap": { "free": 3308840821, "total": 3665190130, "used": { "bytes": 356349309, "pct": 0.097 } }, "total": 11876868165, "used": { "bytes": 8934431706, "pct": 0.752 } } } }Checklist
How to test this PR locally
Run this command from package root
elastic-package benchmark rally --benchmark memory-benchmark -velastic-package benchmark stream --benchmark memory-benchmark -vRelated issues
Screenshots