> 在 2019年7月24日，下午9:48，Hongtao Gao <[email protected]> 写道：
>
> Hi everyone:
> This a discussion about providing a fine grain name rule for service instance
> alarm(may be related to service endpoint).
>
> I'm working on self observability of oap server, that is to collect telemetry
> data from oap backend then inject them into oap self. After analyzing them by
> oap streaming module, the result should be passed through the alarm module to
> generate some notification for the user about what's going on in skywalking
> internal.
>
> Current alarm "include-name" is based on the instance name which is updated
> by cluster coordinator dynamically. As you can see, a static name doesn't
> apply to this scenario.
>
> My idea is to let include-name support regular expression and append service
> name to instance name. So we can config it like "* Service Name" to include
> all of the instances belong to a specific service.
Regular expression is totally OK to me. It just costs a little more CPU.
>
> Other solution, for instance, label system, adding service name field and
> even DSL, are my options, and I also open to new ideas from all of you about
> this stuff.
Label may be better, but we may need a little more design for that, how to set
the instance/service label at first place. Entity structure is there, but we
need to add those.
From my understanding, mesh scenario should be easy today.
Sheng Wu
Apache Skywalking, ShardingSphere, Zipkin
>
> I look forward your reply.
>
> Hongtao Gao
>
> Apache SkyWalking && Apache ShardingSphere
> Twitter, @hanahmily
>
