Comments (13)
I have been working with @nicholasjackson to add the support for Consul Connect! It required k8s metadata to be a part of the envoy metrics. Once that is done, It wouldnt be that hard to add the support for it.
Also, @nicholasjackson has some idea's on improving the spec.
from smi-spec.
Hi @michelleN we have IRC in freenode or Slack in istio.io.
Also you can create any issue in Kiali project as well.
from smi-spec.
I guess what would need to happen is to start work on a Kiali graph "telemetry vendor". Today the only supported vendor is "istio", meaning we directly query prometheus for istio metrics, and we directly query istio/k8s for any additional resource info (namespaces, services, worklods, etc). The root of the code is here. The api
package shows the entry points to graph generation. In telemetry/istio
is the istio
package, holding all of the graph gen code. We'd want to start a new provider like telemetry\smi
that could start serving up a valid TrafficMap
data structure in response to API requests. It won't be super straightforward but perhaps you could use SMI "deployment" resources for "workload" or something like that. Kiali does not try to visualize pod-level metrics, but rather higher level aggregates.
from smi-spec.
I'd love to have a conversation with the Kiali folks to get a list of everything that's missing and what we can do to help out there.
The biggest metrics iteration I'd like to see is hooking up the ability to get a little bit more historical data: query by window, query by date, return a time series.
from smi-spec.
@grampelberg do u know the Kiali folks' github handles? How do we get in touch with them?
from smi-spec.
Alas, I don't have any good connections, just a ton of respect for the product.
from smi-spec.
cc @lucasponce @jotak @jmazzitelli
from smi-spec.
Hi @michelleN @grampelberg ,
We discussed a little bit about that a couple of months ago ( #43 ) but TBH there hasn't been much time spent here on our side. I don't know if there's some news in SMI spec about the items discussed in that issue?
from smi-spec.
@jotak that's a great starting point, I wanted to make sure that was all still valid and such. I'm gonna need to dig into the kiali code a little bit to get a better feel for how you're using everything.
from smi-spec.
The core kiali graph code is here: https://github.com/kiali/kiali/blob/master/graph/telemetry/istio/istio.go
You can see how we utilize the telemetry in Prometheus.
@jshaughn is the subject-matter-expert for that code
from smi-spec.
Alas, I don't have any good connections, just a ton of respect for the product.
@grampelberg thanks for the feedback! Happy to see this.
from smi-spec.
@grampelberg A little while back I re-organized the graph code in Kiali to better prepare for possible addition of a non-istio telemetry vendor. If SMI now offers a fleshed-out API that can front-end Istio it would be a nice experiment to see what we could generate using the SMI telemetry API in addition to having the explicit Istio impl. If promising then we'd be able to potentially provide some support for non-istio mesh, like Linkerd and whatever else that may become available.
from smi-spec.
@jshaughn We now have a functioning implementation of SMI metrics for Istio here. How can we help with getting Kiali to attempt to utilize the SMI metrics APIs?
from smi-spec.
Related Issues (20)
- when to validate traffic target
- `Matches` in `TrafficSplit` is unclear HOT 12
- Add the (required) `apiVersion` field to all YAML file examples HOT 1
- Clarify behavior of overlapping rules and routing resolution in TrafficSplit HOT 1
- Support API/Interface
- Support Exact and Prefix matches for URI path in HTTPRouteGroup
- The Header Match format in HTTPRouteGroup description is not consistent with smi-sdk-go HOT 2
- TrafficTarget should be created in same namespace as destination
- No warning if incorrect yaml is applied for Traffic Split HOT 1
- Logical relationships between multiple match condition in TrafficSplit resource HOT 1
- Trafficsplit based on sourcelabel? HOT 3
- CRD installation HOT 1
- support queryParams in TrafficSpec HOT 1
- Question about A/B testing with traffic splits HOT 1
- Does the TrafficSplit spec allow for identification of a default route for unmatched traffic? HOT 3
- Depreciation of TrafficRoutes in favor of supporting Kubernetes Gateway API - WIP HOT 7
- Question: Header-based TrafficSplit
- Any plans for mirroring?
- State of SMI Spec HOT 6
- CNCF TOC annual review due HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from smi-spec.