You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are extracting code from the onebusaway-watchdog-webapp module and moving it into onebusaway-transit-data-federation and onebusaway-api-webapp in order to flesh out our new, easier-to-use Metrics API that will be used to power our new standalone Watchdog service.
See here for the original PR that added the Metrics API: #395
How to
Adding a new metric to the Metrics API will require you to edit two files:
Hi, I’m working on moving the metrics to the new Metrics API. I noticed that some metrics (e.g., last-update-delta) require agencyId and feedId as parameters, but the current MetricsBean and MetricsBeanServiceImpl don’t seem to support these parameters.
Could you please provide guidance on how to proceed? Should we modify the MetricsBean to include these parameters, introduce a new interface (e.g., getMetrics(String agencyId, String feedId)), or is there another recommended approach? Any advice would be greatly appreciated!
We are extracting code from the
onebusaway-watchdog-webapp
module and moving it intoonebusaway-transit-data-federation
andonebusaway-api-webapp
in order to flesh out our new, easier-to-use Metrics API that will be used to power our new standalone Watchdog service.See here for the original PR that added the Metrics API: #395
How to
Adding a new metric to the Metrics API will require you to edit two files:
onebusaway-transit-data-federation/src/main/java/org/onebusaway/transit_data_federation/impl/beans/MetricsBeanServiceImpl.java
onebusaway-transit-data/src/main/java/org/onebusaway/transit_data/model/MetricsBean.java
The text was updated successfully, but these errors were encountered: