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

feat(logs): add tag attribute autocomplete for logs #2404

Merged
merged 46 commits into from
Apr 6, 2023

Conversation

nityanandagohain
Copy link
Member

@nityanandagohain nityanandagohain commented Feb 28, 2023

Fixes #2248

@github-actions github-actions bot added enhancement New feature or request codeball:needs-careful-review Codeball labels Feb 28, 2023
@nityanandagohain
Copy link
Member Author

I have added TagType in FilterAttributeKeyRequest and FilterAttributeValueRequest @srikanthccv @makeavish

Also in FilterAttributeValueRequest we will need the type of FilterAttributeKey so that we can query the correct column. I am suggestion to add FilterAttributeKeyDataType thoughts ?

@SigNoz SigNoz deleted a comment from github-actions bot Feb 28, 2023
@makeavish
Copy link
Member

@nityanandagohain Why do we need tagType in request?

Also FilterAttributeKeyDataType can be added as it will be useful for cases where a tagKey is same but data type is different.

@nityanandagohain
Copy link
Member Author

in autocomplete for keys, I think we can ignore TagType as we can return both attribute and resource keys

In autocomplete for values, we need to know the tagType, DataType of the key.

@makeavish
Copy link
Member

In that case, we need tagType.
cc: @srikanthccv

@srikanthccv
Copy link
Member

I have added TagType

The TagType will contain if it is a column, tag, or resource? This is fine.

Also in FilterAttributeValueRequest we will need the type of FilterAttributeKey so that we can query the correct column.

It is there https://github.com/SigNoz/signoz/pull/2244/files#diff-d3c63967220d7c8ed701bb4ec8f3ec8fe5a24a5264477429dfc209ca5a269374R76

Also fine with the DataType.

It would be easy to review and follow this here #2244 as you can make suggestions directly there.

@sonarcloud
Copy link

sonarcloud bot commented Mar 6, 2023

SonarCloud Quality Gate failed.    Quality Gate failed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 19 Code Smells

No Coverage information No Coverage information
23.3% 23.3% Duplication

@nityanandagohain nityanandagohain marked this pull request as ready for review March 31, 2023 11:09
@makeavish
Copy link
Member

@nityanandagohain I see that you are not creating a separate function for fetching aggregates attributes, I think there can be a future use case to return filtered attributes based on aggregate operator

@nityanandagohain
Copy link
Member Author

@srikanthccv so you are asking if a key is missing in how tag_attributes table then how should it be handled in our query range v3 API right?

Or you are asking about value suggestion? as value suggestion won't be possible if key is not present.

@nityanandagohain
Copy link
Member Author

@makeavish @srikanthccv the aggreateAttribute function is added now.

Copy link
Member

@srikanthccv srikanthccv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just one question, LGTM.

@srikanthccv
Copy link
Member

Leaving it yourself to merge just in case if you want to test it more or make any minor changes.

@nityanandagohain nityanandagohain merged commit d092905 into develop Apr 6, 2023
@nityanandagohain nityanandagohain deleted the issue-2248 branch April 6, 2023 08:02
@srikanthccv
Copy link
Member

@nityanandagohain I only see the top-level fields in the staging app. Are there no other attributes? Can you make it so that there will be some attributes of different types for testing and developing for frontend folks?

@nityanandagohain
Copy link
Member Author

@srikanthccv we have to deploy the signoz_otel_collector, have we done that ?

@srikanthccv
Copy link
Member

Yes, that must have happened since your collector PR merged first, so images would have been pushed. @prashant-shahi earlier said to take care of that and it will work.

@prashant-shahi
Copy link
Member

@srikanthccv And open API for health and version of the signoz-otel-collector (perhaps via query-service) would have been very helpful.
That way, we can display the otel version in SigNoz UI as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
codeball:needs-careful-review Codeball enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

(logs): tag filters suggestion API for explorer
5 participants