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

[1.2.2 Develop] Bring consistency to Data Query Index Types #2391

Closed
RadekHvizdos opened this issue Feb 10, 2019 · 3 comments
Closed

[1.2.2 Develop] Bring consistency to Data Query Index Types #2391

RadekHvizdos opened this issue Feb 10, 2019 · 3 comments
Labels
resolved A fixed issue

Comments

@RadekHvizdos
Copy link

Dear developers,

I have noticed that creating new graphs for interfaces, and disk space results in different default Data Query Index Types:

Disk space is by Index:
image

Interfaces are by Name:
image

Could we do some of the following:

  • Change the default setting to dskPath for the Disk Space query
  • Allow the user to choose which Index Type is used during graph creation time. I was thinking this should be exposed as part of 'Advanced' graph/datasource creation mode.

Thank you!

cigamit added a commit that referenced this issue Feb 10, 2019
[1.2.2 Develop] Bring consistency to Data Query Index Types
@cigamit
Copy link
Member

cigamit commented Feb 10, 2019

Please review the change here. Next time you have a suggestion like this, it might just be as easy to create a pull request.

The second part of your request, I would like you to create a separate issue for please. It's not good to mix a bug and an enhancement in the same request.

@cigamit cigamit added the resolved A fixed issue label Feb 10, 2019
@cigamit
Copy link
Member

cigamit commented Feb 10, 2019

Simply, update the resource file and re-index the devices. You will get a warning message that the indexes are changing. Also, note that if it's not compatible for the primary key, you will also receive a warning.

@cigamit cigamit closed this as completed Feb 10, 2019
@RadekHvizdos
Copy link
Author

Thank you.

Yes I will do as instructed.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
resolved A fixed issue
Projects
None yet
Development

No branches or pull requests

2 participants