Not all events contain the qmgr name this way we can guarantee it’s always there. I also added the queue manager name into the generated output as that may be useful. There are other ways to do that transform without needing another program, but it was quickest to do it that way. Since Loki’s ingestion process likes to work with single-line log messages, I added a call to the jq program so that the pretty-printed JSON events get transformed into single-line JSON. The amqsevt sample program, which I’ve written about before, is used to format the events.
Mqm calculator full#
For example, if I’d consumed all events, a simple script could be used to force creation of configuration or queue full or authorisation events. One reason for that was the hope that I could demonstrate selection based on fields such as the event type another reason was that it’s easy to generate more test data on-demand.
I considered using MQ’s error logs for this experiment as they have an option to be written in JSON format.īut instead I decided on working with event messages. The first thing to think about was what data might be useful and suitable for storing in Loki. One store is dealing (mostly) with numbers the other is dealing (mostly) with text.įor more information about Loki, there is a fuller introduction here. As it comes from the same stable, Grafana then has access to Loki built in as a regular datasource.Ĭontrast that with metrics data, stored in a time-series database such as Prometheus. Essentially it takes lines of information that you might find in product or platform status logs, stores them, and provides a way to search or dig deeper into them. It has a similar role to Elasticsearch and Splunk although its creators will naturally point out differences. Loki is Grafana’s version of a log aggregation tool. On the way I’ll also take a brief digression into using logrotate. And so I have done some very quick experiments to prove that the approach really can work. Especially when I have a reasonable starting point like a working local Grafana setup. Which was my reply.īut of course, I’m not likely to leave it there when I learn about a new tool. Instead after a very short search and a few minutes reading, I guessed that it ought to be possible to use it. My immediate reaction was that I didn’t know what Loki was in this context, but clearly they couldn’t be asking about a Norse god or Marvel character. Specifically would it be possible to use Loki and Grafana together with MQ. Because of the projects and articles I’ve written about visualising MQ’s metrics in Grafana, I recently had a couple of people asking about using that same front-end but able to work with log-file data. It is odd how often similar questions come at the same time from unrelated places.
0 kommentar(er)
