AcademySoftwareFoundation / AcademySoftwareFoundation/OpenCue

Metric mismatch between proto and elasticsearch

Open
#2,151 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Python
Stars
957
Forks
259
Avg merge
3d 6h
Merged PRs (30d)
16

Description

**Describe the bug**
Some stats fields in elasticsearch are missing maybe due to a mistmatch between what is send to kafka, and what the monitoring-indexed is expecting.

**Expected behavior**
Metrics should match

**Screenshots**
Metrics related to stats are missing in elasticsearch :
Image

Here what's kafka is receiving from cuebot :
Image

what's the monitoring-indexer is expecting :
Image

And what's the job.proto is supposed to send
Image

The documentation also doesn't seems to reflect the schema we are expecting : https://docs.opencue.io/docs/reference/monitoring-reference/#event-payload-schemas

Image

Not sure if its related, but if i try to execute : opencue.wrappers.monitoring.getFarmStatistics()

I got this error :

```grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNIMPLEMENTED
details = "Method not found: monitoring.MonitoringInterface/GetFarmStatistics"
debug_error_string = "UNKNOWN:Error received from peer {grpc_status:12, grpc_message:"Method not found: monitoring.Mo
nitoringInterface/GetFarmStatistics"}"
```

**Version Number**
1.15

Contributor guide

Open the contributing guide

Research direction

Compare the schemas shown for job.proto, Kafka's cuebot payload, the monitoring-indexer expectations, and the monitoring reference documentation. Start by tracing the stats fields across those entry points and reproduce the getFarmStatistics() call; done means the stats metrics match in Elasticsearch, the documentation reflects the schema, and the RPC no longer reports UNIMPLEMENTED.

Written by the indexing model from the issue text.

Assessment

Tech stack
elasticsearch, grpc, kafka, python
Domain
api, databases, distributed-systems, observability-sre
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.