Skip to content
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

Prometheus monitoring fails when app name contains a UUID #861

Open
BuddhiWathsala opened this issue Jan 22, 2020 · 0 comments
Open

Prometheus monitoring fails when app name contains a UUID #861

BuddhiWathsala opened this issue Jan 22, 2020 · 0 comments

Comments

@BuddhiWathsala
Copy link
Contributor

Description:
In Kubernetes deployment of Siddhi apps, especially in a distributed deployment, the Siddhi parser will concatenate a UUID to the Siddhi app name as below.

@App:name("5.DelayAlert-979d46e5-3a47-4db8-ad81-682238f2f19c-1")

In that case, the Prometheus monitoring of the Siddhi app did not show any useful information.

A sample executable query given by the Siddhi Prometheus server is as follows.

io_siddhi_SiddhiApps_5_DelayAlert_979d46e5_3a47_4db8_ad81_682238f2f19c_1_Siddhi_OnDemandQueries_query_latency

Suggested Labels:
Bug

Affected Product Version:

  • Siddhi runner 5.1.2
  • Siddhi operator 0.2.2

Steps to reproduce:
Try the TFL use case in K8s here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants