Export metrics to dynatrace using Micrometer.io
gradle dependency 'io.micrometer:micrometer-registry-dynatrace:latest.release'
version - (1.1.3)
Causing Exception -> Error {"error":{"code":400,"message":"Could not map JSON at 'series[33].dataPoints' near line 1 column 4071"}} {}
metrics:
export:
dynatrace:
device-id: xxxxx
uri: https://xxxx/e/xxxxx/api/v1/entity/infrastructure/custom
api-token: xxxxxxx
enabled: true
technology-type: java
step: 1m
I have found the issue with latest micrometer release(1.1.3). While forming Json data from the metrics its throwing exception i went one minor version(1.1.1) older it worked fine. Should open the bug for this.
Error
{"error":{"code":400,"message":"Could not map JSON at 'series[33].dataPoints' near line 1 column 4071"}} {}
We are getting this error while its trying to convert the CPU metrics to json
Related
My Artifactory logs are showing the following errors with alarming frequency. The metadata service is up and healthy according to Artifactory, and aside from the log spam, it doesn't seem to be causing any problems. Does anyone have any ideas how to fix this?
[jfrt ] [ERROR] [af10ed1c492f4e88] [s.MetadataEventServiceImpl:346] [art-exec-6 ] - Unable to send statistics event to Metadata Server. Caught exception: Failed executing api/v1/stats, with response code: HTTP/1.1 500 Internal Server Error and response message: {"cause":"Internal error while processing request","message":"Failed to update stats with error couldn't find versionIDs for the given paths: couldn't find versionIDs for the given paths"}
Artifactory 7.27.10, running in Kubernetes
Using an external postgres 13 database
Using s3 as the storage backend
This is a known issue (documented internally as META-1180). This has been fixed and is released with Artifactory 7.29. This version of Artifactory is scheduled for release sometime over the next few weeks.
Exception while generating C# code voor TSI API.
git clone https://github.com/Azure-Samples/Azure-Time-Series-Insights.git
cd Azure-Time-Series-Insights\csharp-tsi-preview-sample\DataPlaneClient
.\GenerateCode.bat
AutoRest code generation utility [cli version: 3.0.6187; node: v12.16.3, max-memory: 8192 gb]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
NOTE: AutoRest core version selected from configuration: ~2.0.4413.
Loading AutoRest core 'C:\Users\michelh\.autorest\#microsoft.azure_autorest-core#2.0.4417\node_modules\#microsoft.azure\autorest-core\dist' (2.0.4417)
Loading AutoRest extension '#microsoft.azure/autorest.csharp' (~2.3.79->2.3.84)
Loading AutoRest extension '#microsoft.azure/classic-openapi-validator' (~1.0.9->1.0.14)
Loading AutoRest extension '#microsoft.azure/openapi-validator' (~1.0.2->1.0.4)
Loading AutoRest extension 'oav' (~0.4.20->0.4.70)
Loading AutoRest extension '#microsoft.azure/autorest.modeler' (2.3.55->2.3.55)
VERBOSE: Validating 'file:///C:/source/experimental/azure/p2/Azure-Time-Series-Insights/csharp-tsi-preview-sample/DataPlaneClient/azure-rest-api-specs/specification/timeseriesinsights/data-plane/Microsoft.TimeSeriesInsights/preview/2018-11-01-preview/timeseriesinsights.json'
VERBOSE: Validating 'swagger-document'
TypeError: jsonPath.nodes is not a function
at openApiValidationExample (C:\Users\michelh\.autorest\oav#0.4.70\node_modules\oav\dist\lib\autorestPlugin\extension.js:75:40)
at async analyzeSwagger (C:\Users\michelh\.autorest\oav#0.4.70\node_modules\oav\dist\lib\autorestPlugin\extension.js:34:38)
at async C:\Users\michelh\.autorest\oav#0.4.70\node_modules\oav\dist\lib\autorestPlugin\extension.js:48:70
at async Promise.all (index 0)
at async C:\Users\michelh\.autorest\oav#0.4.70\node_modules\oav\dist\lib\autorestPlugin\extension.js:49:5
at async C:\Users\michelh\.autorest\oav#0.4.70\node_modules\#microsoft.azure\autorest-extension-base\dist\lib\extension-base.js:39:17
FATAL: TypeError: jsonPath.nodes is not a function
FATAL: swagger-document/model-validator - FAILED
FATAL: Error: Plugin model-validator reported failure.
Process() cancelled due to exception : Plugin model-validator reported failure.
Error: Plugin model-validator reported failure.
Can you share the documentation details which you are following? Are you referring to Azure Time Series Insights Gen1 or Gen2?
Please see the sample Azure Time Series Insights Preview - Data Plane Client Sample App and let me know if that helps.
Ensure you have the all prerequisites and also Ensure to Update timeseriesinsights.json as needed.
I try to run the example CorDapp following this url https://docs.corda.net/tutorial-cordapp.html
But there is error while building Nodes as below error
[ERROR] 15:40:44+0700 [main] internal.NodeStartupLogging.invoke - Exception during node startup: Certificate is not valid at instant now [errorCode=18292z7, moreInformationAt=https://errors.corda.net/OS/4.0/18292z7]
So I understand that if I set devMode=true, the certificate for each nodes won't required but after I configured devMode=true, still does not work.
Update 1:
I installed Windows into VM and do the tutorial. Nodes built successfully on VM. Still looking for the solution.
Finally, I figured it out. After I checked X509Utilities.kt which this error came from.
There is some Date validation. So I changed Format and Date format in Windows Region menu as below image. It works!!
Date format image
I am playing around with a small project derived from here: https://github.com/corda/cash-issuer.
This repo is building on unreleased corda 4.0 version (Snapshot).
I've written a small script to issue cash via rpc client, which worked fine.
I can query the vault from the interactive shell and get the correct result:
run vaultQuery contractStateType: net.corda.finance.contracts.asset.Cash$State
states:
- state:
data: !<net.corda.finance.contracts.asset.Cash$State>
amount: "10000.00 EUR issued by O=PartyA, L=New York, C=US[01]"
...
However, it fails to do the same query in an api hosted in the integrated webserver:
#GET
#Path("balances")
#Produces(MediaType.APPLICATION_JSON)
fun getBalances() : List<Cash.State> {
return rpcOps.vaultQueryBy<Cash.State>().states.map{it.state.data}
}
fails with
[ERROR] 19:21:57+0100 [Thread-3 (ActiveMQ-client-global-threads)] internal.RPCClientProxyHandler.artemisMessageHandler - Failed to deserialize RPC body [errorCode=15rlwi0, moreInformationAt=https://errors.corda.net/OS/4.0-SNAPSHOT/15rlwi0]
Failed to deserialize RPC reply: net.corda.core.utilities.Try$Success (erased) -> value(*) -> net.corda.finance.contracts.asset.Cash$State: Requested interfaces must consist only of methods that start with 'get': net.corda.core.contracts.FungibleAsset.withNewOwnerAndAmount
I'm on a windows10, nothing special.
As Tbltzk notes, this is a bug that was fixed as part of r3-cev.atlassian.net/browse/CORDA-2330.
Corda's snapshot releases undergo less testing than official releases, and are thus more likely to contain bugs.
pact-jvm-provider-maven_2.11 works with Java8, but not Java7. Getting the following error
[ERROR] Failed to execute goal au.com.dius:pact-jvm-provider-maven_2.11:3.5.0:verify (default-cli) on project product-xapi-service: Execution default-cli of goal au.com.dius:pact-jvm-provider-maven_2.11:3.5.0:verify failed: Unable to load the mojo 'verify' in the plugin 'au.com.dius:pact-jvm-provider-maven_2.11:3.5.0' due to an API incompatibility: org.codehaus.plexus.component.repository.exception.ComponentLookupException: au/com/dius/pact/provider/maven/PactProviderMojo : Unsupported major.minor version 52.0
I don't see the mention of requirement of Java 8 as well. Does it support Java 7 at all?
Actually, i find the documentation specifying the versions here https://github.com/DiUS/pact-jvm. Thanks.