-
Notifications
You must be signed in to change notification settings - Fork 436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Service logs support via Generic Extensions #486
Comments
Have you tried implementing log-drain type bindings? https://github.com/openservicebrokerapi/servicebroker/blob/master/spec.md#log-drain The broker author has to support this type of binding. |
@n3wscott sorry for late response. I understand the log-drain binding type enables a service to collect logs from an application through a syslog endpoint (e.g. application logs search/archive/alerting). This issue is more about services pushing service related logs to applications. |
As @gberche-orange, syslog drains allow service instances to receive logs from applications rather than the other way around. Do we think this issue would be solved by the extensions proposal (#431), whereby service instances could host an endpoint that applications could poll to fetch logs? |
I realize I misworded the issue, so I updated it to reflect that service logs would need to be consumed by app developers first, and then potentially by app themselves:
In the case of cloudfoundry, consumption of application logs by developers is standardized through the loggregator support (with both CF CLI and streaming to log management systems UX). I believe it would make sense that service instances logs get consumed by app developers through the same UX. This may require platforms to poll a service provided endpoint, and stream the service instances logs through the log pipeline. Additionally, service brokers could return log polling endpoint in their binding responses so that apps can poll them, in order to automate service instance logs processing. Maybe OSB support for log endpoint in binding responses would help keep a consistent experience across services. |
Thanks for the clarification @gberche-orange! That makes sense to me. I think this feature request can be broken down into two parts:
Does that make sense? I believe we should track part (1) in this issue (developing the OpenAPI standard for fetching logs from service instances), and part (2) will be tracked by platform authors in their respective forums. |
thanks @mattmcneeney . Sounds good to me. For clarity, would part (2) also cover how platforms would be presenting log endpoints to applications, in similar way than service binding credentials are injected to applications by platforms ? |
Yes I believe so! |
For the CF community, the related epic in SAPI backlog, if this may help follow CF exchanges on the topic. |
Closing this. Work on the generic extensions work can be tracked in #670 ! |
Reopened, updated title and added the blocked label so that we tackle this after the generic extensions (#670) work is done. |
As a service user:
As a broker author, in order to provide logs to service users and bound apps, I need a standard way of exposing metrics to platforms, in particular, I need:
Related pointers:
The text was updated successfully, but these errors were encountered: