Hi @Michael Jobe 

Yes, you can post here or open a WRC ticket.

The error usually denotes a privilege issue. I see that the file name is not the default we ship the product with. That is isc_prometheus.yml. Also the file should have privileges set to 764 or rwxrw-r---

Another important thing would be to use the start.sh script that checks for the correct privileges on directories and files.

Let us know how you get on.

Thanks

Hi Raj:

This article is not about AWS but it clearly explains how to set it up with Gitlab so I hope you can find your answers.

If you use containers, when you build them you'd be installing your solution code from a file or a series of files. you'd probably be copying them in the container and importing and compiling them. You could also do that before and just copy in the container the IRIS.DAT containing the code.. it depends.

You should also look and consider the ZPM package manager for packaging and moving your code around.

I hope this is of some help in your investigation

@Henrique Dias, Way to go! 

I'm very happy and always excited to see how new APIs are leveraged by the community.

You have just enhanced the InterSystems IRIS native (no need to install anything) Prometheus exporter & by doing that you have just shown how application developers can start thinking and implement their application performance monitoring (APM) and use an existing framework and API.

There soon be other news on this subject, stay tuned!

Good, well-detailed article with links and explanations

Great job Henrique!