You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Where it would be the "ElasticsearchMetrics" logger that should cover the metrics parts if I have read the documentation correctly.
The reason why I have this configuration present:
stagemonitor.reporting.elasticsearch.url
is just to see if would make any difference to get the metrics working. It would also no work without that configuration.
Would anybody know what could be wrong. Or would maybe have working configuration / application they can share where the metrics are written to a logger instead of to the Elasticsearch endpoint.
Best regards
Lars Milland
The text was updated successfully, but these errors were encountered:
Hi
I am trying get StageMonitor to output the metrics that usually go to ElasticSearch to a console logger, with logback. But
I can't seem to get anything of metric sample kinds to work.
I have this StageMonitor configuration:
The application that I am trying this on is a Java Spring Boot application, where I have this for starting up StageMonitor:
Running my application I can see that StageMonitor is working - see attachment:
stagemonitor.txt
I can also see that my logback configuration should be working, as the StageMonitor span traces are printed to my console.
I have this in my logback configuration which should match the two loggers that I can expect StageMonitor to use:
Where it would be the "ElasticsearchMetrics" logger that should cover the metrics parts if I have read the documentation correctly.
The reason why I have this configuration present:
stagemonitor.reporting.elasticsearch.url
is just to see if would make any difference to get the metrics working. It would also no work without that configuration.
Would anybody know what could be wrong. Or would maybe have working configuration / application they can share where the metrics are written to a logger instead of to the Elasticsearch endpoint.
Best regards
Lars Milland
The text was updated successfully, but these errors were encountered: