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

disable graphs at service manually or automatic? #9

Closed
mkayontour opened this issue Mar 9, 2017 · 6 comments
Closed

disable graphs at service manually or automatic? #9

mkayontour opened this issue Mar 9, 2017 · 6 comments
Assignees
Milestone

Comments

@mkayontour
Copy link

Hi there,

is there anything implemented which allows me to disable graphs for a specific service?
Would be great to disable some service instead of having a empty.
empty-graph

I'm not a developer otherwise i would implement something and contribute.

@mkayontour
Copy link
Author

Problem solved: graphs get disabled if no perfomance_data is active at the service

But if I need the performance data but not the graph in the webinterface is still a issue for me. ;)

@mkayontour
Copy link
Author

link to PR #11

@Aleksey-Maksimov
Copy link

I do not agree that the problem is solved.
In my opinion, it is better to make graphics visible only to those services for which they are explicitly configured in /icingaweb2/grafana/graph.
For example, I have a lot of services and many of them graphic is not needed.

@Mikesch-mp Mikesch-mp self-assigned this Apr 22, 2017
@Mikesch-mp
Copy link
Owner

I have 2 ideas now for that problem.

  • config option to show only configured graphs
  • config option for a custom variable, that if set the graph will not be displayed

Would that fit your needs ?

@janvonde
Copy link

+1 for the custom variable in icinga2

@Aleksey-Maksimov
Copy link

Both options :)

@Mikesch-mp Mikesch-mp added this to the 1.2.0 milestone Apr 24, 2017
@Mikesch-mp Mikesch-mp modified the milestones: 1.1.5, 1.2.0 May 22, 2017
epinter pushed a commit to epinter/icingaweb2-module-grafana that referenced this issue May 23, 2017
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

4 participants