Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Feast Ingestion not exporting success metrics to statsd #747

Closed
pmjacinto opened this issue May 27, 2020 · 3 comments
Closed

Feast Ingestion not exporting success metrics to statsd #747

pmjacinto opened this issue May 27, 2020 · 3 comments
Labels
kind/discussion wontfix This will not be worked on

Comments

@pmjacinto
Copy link

Expected Behavior

The dataflow step WriteSuccessMetrics should be executed and produce metrics.

Current Behavior

In the previous step, the "dummy" PTransform always seems to output zero rows.
https://github.com/feast-dev/feast/blob/v0.5.0/storage/connectors/bigquery/src/main/java/feast/storage/connectors/bigquery/writer/BigQueryWrite.java#L93-L105

This leads to the metrics transform never getting any inputs.

Is this an expected behaviour?

Screenshot 2020-05-27 at 16 32 13

---

Screenshot 2020-05-27 at 16 32 34

Steps to reproduce

  • Create an ingestion pipeline
  • Ingest a row
  • Check dataflow metrics

Specifications

  • Version: 0.5.0
  • Platform: GKE, Dataflow
  • Subsystem: Feast Ingestion

Possible Solution

@woop
Copy link
Member

woop commented May 30, 2020

Hi @pmjacinto

Thanks for raising this. I believe the comment that you linked to does indicate the problem: BigQueryIO does not emit successful writes, meaning we can't emit metrics. WriteSuccessMetrics is an IO agnostic step that is always generated. For the time being we emit total rows processed and failed metrics, the difference of which should give you an estimation of rows written.

@woop
Copy link
Member

woop commented Jun 7, 2020

@Yanson @pmjacinto for your information, the latest addition to BQ ingestion will have success metrics again #757

@stale
Copy link

stale bot commented Aug 6, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix This will not be worked on label Aug 6, 2020
@stale stale bot closed this as completed Aug 13, 2020
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
kind/discussion wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants