Member since
06-17-2023
5
Posts
0
Kudos Received
0
Solutions
03-11-2025
03:07 AM
Hello @Deepak_Unravel I highly recommend you to go through the links which I have given in my previous comment. As mentioned above, timeseries data not stored in any of the backend database. It uses LDB [leveldb] storage. If you haven't tried the API Explorer feature in your environment, I request you to try out the same. I have given below the example query which I have tried in my lab using API Explorer to get the HDFS Service Health status for the last 7 days. Navigate to CM UI -> support -> API Explorer -> TimeSeriesResource -> GET /timeseries API call. Example query: Please note to replace the {cm_server_fqdn} & {cm_server_port} curl -X GET "https://{cm_server_fqdn}:{cm_server_port}/api/v57/timeseries?contentType=application%2Fjson&desiredRollup=RAW&from=2025-03-04T09%3A45%3A00.000Z&mustUseDesiredRollup=false&query=select%20health_good_rate%20*%20100%20as%20%22good%20health%22%2C%20health_concerning_rate%20*%20100%20as%20%22concerning%20health%22%2C%20health_bad_rate%20*%20100%20as%20%22bad%20health%22%2C%20health_disabled_rate%20*%20100%20as%20%22disabled%20health%22%2C%20health_unknown_rate%20*%20100%20as%20%22unknown%20health%22%20where%20entityName%3D%22HDFS-1%22&to=now" -H "accept: application/json" If you have any business requirement to create the custom query/chart you shall make use of the timeseries data. For more details, kindly refer https://docs.cloudera.com/cdp-private-cloud-base/7.1.9/monitoring-and-diagnostics/topics/cm-charting-time-series-data.html Also consider reach out to Cloudera Support.
... View more
04-02-2024
07:26 PM
@Deepak_Unravel This is a regression on the python3 upgrade or more specifically something that worked by mistake in the past. Before py3 avro used to be more flexible with it's schema's and used to ignore any extra fields. If a value didn't exist in the schema it could have any value without invalidating the parcel. Now it expects data to be in exact format to the schema which is more accurate. During the py3 migration most fields were added but looks like we missed the conflicts field. A workaround for now can be to remove the conflicts field from the parcel since it doesn't have any conflicts right now. Please remove the conflicts entry in /opt/cloudera/parcels/UNRAVEL_SENSOR-1.0.4791002_cdh7.1_h3.1_s2.4/meta/parcel.json file on all the agents. Post conflicts entry removal you will able to distribute the parcel.
... View more