-
Notifications
You must be signed in to change notification settings - Fork 456
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
[Prototype] TSDB For Oracle Integration #4848
Comments
|
metrics-oracle.performance@package
|
|
This task is related to similar effort put under #4749 |
One problem i face is , i do not know if a field is a dimension or not. It may be good that in kibana discover view, there exist an icon if the field is a dimension field or not. @ruflin , do you agree?
|
Going with the documentation , the document must have a But, the document in my performance datastream does not contain this field. This makes me wonder, if it is really a timeseries document!! Also, the _tsid field does not appear in the UI , under meta fields
@ruflin , @jsoriano , have you seen the |
PR : #4966 |
@agithomas what version of Kibana are you using? It seems that support for |
docker.elastic.co/kibana/kibana:8.7.0-SNAPSHOT is what i am using at present |
@agithomas I like the idea that Kibana in the UI would indicate if something is a dimension or not. Could you file an issue in Kibana for this? For the SNAPSHOT, make sure to pull down the most recent versions. Quite a few fixes landed over the last few days. What I often do for debbuging purpose is looking at the mapping of the current write index of the data stream (instead of the template). |
Closing this issue. A meta issue is created under Observability-dev to track in detail |
[Prototype] TSDB For Oracle Integration #4848
TSDB settings are enabled for Oracle integration in Kibana for Enabling and disabling.
Validate that if TSDB is already enabled, switch back to standard index type is disabled.
Enable Timeseries settings in manifest.yml for performance datastream
PR Details : #4966
The text was updated successfully, but these errors were encountered: