Hi,

why are you doing the separate step of checking out your sources outside of eclipse/Atelier? You can do that directly in there, which would simplify your workflow to something like this:

  1. Checkout repository in EGit into an Atelier project
  2. Create ticket123 branch
  3. Make your modifications
  4. Submit your modifications into the branch
  5. Merge branch into master as necessary

Best,
Fab

"We want our code to be as accessible and readable as possible to as many people as possible. "
Do we? ;)
"We always prefer whitespace formatting and curly brackets to arcane one line syntax." -- I don't ;)
Using arcane one liners shows that you are a superiour wizard. One should always use the short forms of commands to make code more terse and save space. If people want to read the code, they can use 'expand code' in studio (which expands the shortform commands to the full version).
Note, there might be some sarcasm in here.
People who know me, might also know that I'm only maybe 80% joking;)

There really isn't a general answer as to what the 'best way' (tm) is. There are way too many dependencies on that.

It really depends on your workflow and requirements of your backend. Zabbix is very well capable of ingesting SNMP data, just as well as ODBC (https://www.zabbix.com/documentation/3.4/manual/config/items/itemtypes/snmp).

Usually the answer to 'the best way' comes down to: what are you most familiar with? To use ODBC you'd need to implement some glue code on the Caché side, same if you were to go with a REST interface. Since you mentioned you have custom indicators, you'll have to write some code in any case. So, again, it comes down to your preferences and preexisting experiences.

Evgeny already pointed out one of the local SNMP articles to get you started on this.

Cheers,
Fab